Could the midday solar power glut be used to spin up flywheels, then be used with generators to provide the late afternoon air conditioning power?

Thank you for balancing the parentheses. Cosmic order has been restored.

The answer is that this is somewhat misleading; there are plenty of Z80 compatible chips still being manufactured. The TI-84 uses the eZ80, which is four times faster and will still be around. There are also many (many) clones that are closer to cycle-exact.

The agony, of course, is that Dieter Rams was all about function, which informed his designs. If Apple had hired him (he's still alive, incredibly) instead of just imitating him, he'd probably have taken a significantly different direction that actually respected the complexity of the underlying hardware instead of trying to butcher it. And the logos would have been smaller!

The ARM64 version of Windows 11 has emulators for both x86-32 and x86-64 applications, and it works for most programs.

Getting a player's game process to execute arbitrary code is "hacking the two players' computers directly", so their statement is BS.

It's pretty easy to compress:

Integral from -1 to 1 of (1/sqrt(1 - x^2)) dx.

0.121121112111121111121111112... is irrational, but I can tell you with just some quick calculations that the 150,000,000,000,000th digit is 1. (The 150,000,007,349,285th digit is the next 2.)

The last part, the right to petition the Government for redress of grievances, is what this is about. You have a right to complain to government officials, though of course they don't have to care. Blocking someone on a social media account that is used for official government messaging is blocking such "petitions".

Personally I found this really eye-opening, so...

As they say, if buying isn't owning, piracy isn't stealing.

The story is an exclusive interview with a significant player in the OSS community, and it addresses an important and pressing matter. That is entirely aligned with Slashdot's mission, no matter who's publishing it.

I don't really like El Reg either; its general style can only really be described as a self-parody of whiny bitterness, and I've always found it rather dated, like something that should've been left for dead between the stickiest pages of a White Dwarf magazine in the late eighties. However, this story seems to be free of any of that, which is perhaps a good sign.

I don't disagree with you, but as far as I can tell even the colon isn't necessary for Crockford's syntax to be unambiguous, which annoys me.

It didn't take long to read through the entire Misty spec. Basically it's the software equivalent of a conlang: there's only one short program written in the language, no actual implementation, and it includes a bunch of slightly insane features that would be annoying as hell to actually use. Here are some highlights:

  - The syntax for variable assignment is set foo: bar — I initially let this one slide since Doing Weird Things With Colons is a big part of the Make Parsers Dumb Again revolution of the past 10 years or so, but in retrospect it kinda looks like the creator's imagination is being subsumed by the legacy of JSON...
  - Many operators are not ASCII. Throw out / * = and adopt their Unicode equivalents! Have fun learning how to make your keyboard do any of that.
  - Question marks in variable names for marking predicates and booleans! Schemers, start your grudging!
  - Some very conspicuous Not Invented Here terminology: arrays are either "stone" or "antestone" (immutable or not—just call them 'final'!)
  - Lots of Crockford's other pet projects get screentime: numbers are always stored in his DEC64 format (a 64-bit float with a 56-bit mantissa and an 8-bit decimal exponent), there are native functions for handling strings encoded in a variant UTF-8 format that's slightly more dense, and it seems JSON has been updated to Nota (mainly by making commas and quotes around field names implicit where possible).
  - Probably the biggest pet project, patterns are embedded directly into the spec and don't seem to have any other documentation. The gist is that they're regexes with indenting (not an innovation) and slightly less hairy names for common character classes. The goal of fixing regexes is admirable, but I think more research should have been done on what the state-of-the-art in regex legibility actually looks like, rather than starting from vintage 90s PCREs. At any rate, I don't think the rework is radical enough.
  - An attempt at handling parallelism through a fairly unremarkable message-passing system called actors, which is more like a multi-process RPC API than a threading model; there is no way to have multiple threads sharing access to a variable. Should the sharp knives be hidden from the children? You decide!

Must you refer to Sundar Pichai this way? It's very offensive to the shareholders.