tensility

What if I hope for a genie to emerge from a lamp in order to grant me wishes?

Okay, but does it support comments?

Agreed. Lack of CarPlay support is just one of the reasons that I won't own a Tesla. (Also, I prefer not to support anything tainted by Elmo's toxicity.)

Agreed. CarPlay support is table stakes fo me fir my next vehicle, no matter how good its native UI is.

Trying to figure out whether this statement was intended as sarcasm or if it's willfully blind to decades of rising surveillance capitalism as business model.

The only reason it doesn't is the greed of folks who become billionaires.

This...100%

Guillotines are the classic method, and they are likely coming if we don't change course.

Well, with the extreme levels of income stratification that we have in the US and greater world, money literally means a different thing to the few folks who've escaped the poverty trap ... just like hunting means a different thing for the hunters as it does for the prey.

It's all interesting advertising / news; however, why does it have to constantly cost me five precious vertical lines of text worth of screen real estate in Claude Code that apparently can't be dismissed? FFS

Certificate expiration timeline...

Cool. Now go check out Mojo.

SICP should probably be required reading in the CS curriculum. It's a great start at understanding register hardware simulation.

Yeah, that was not at all my experience in CoreOS/SWE, where we would sometimes/often have to wait weeks for submissions to turn around in B&I to become part of "daily" builds. Glad you don't have to put up with the same ridiculous crap process.

A statement which goes to show that confusing correlation with causation is all you need.

The fixing of a bug at Apple is the easy and quick part. It's the submission process from then until it gets released as part of an OS update that is the ridiculously long (and too often difficult) part.

It would have to be a very serious security bug. Even then, unless they've totally upended their software development workflows in the past couple of years, the Apple I knew extremely well from the inside couldn't turn around a software fix this quickly, from PR to OS release, even if its existence depended on it. There's simply too much bureaucracy and process around submitting anything, no matter how vital.

At a very low level, it is. I know the individual that made a "diagnostic" for the floppy drive while working as a tech on the Apple I and Apple II designs which caused the drive to whine in patterns that were distinctly ... orgasmic.

If I recall correctly, when you wanted all of the bells and whistles that Slackware had to offer, it required 72 floppy disks.

Bring back Slackware?

The fruit company still has an internal culture, especially in hardware-focused teams, with a relentless focus on shipping products followed by iterative refinement.

So, should we assume that they vibe-coded this patch? Sad...

Meanwhile, I've had the same blender for thirty years, and it's still going strong.

I would love to go back to more skeumorphic system interfaces. The layered panes of glass metaphor has been a pain in the ass from a usability perspective from the get go, enough so that I cheered to hear of Alan Dye leaving Apple.

One of the few languages I've known that didn't provide any standard features for libraries (until the sixth major revision), Scheme, has been the worse for it.

Not giving real output is a complete fail. Try again.

This.

Oh, it would be nice if it were just feature size. Over the prior 15 years, the nand industry has doubled its logical density three times over with the trick of encoding more than one bit per physical voltage well, making the error bounds on leaking wells tighter and tighter and amplifying the bit rot impact, in number of ECC corrections consumed, per leaked voltage well.

At the physical device layer (i.e. what a nand controller vendor programs to), a nand flash device that supports ONFI 2 SLC Mode can be configured to use (some of) its blocks in SLC mode rather than MLC/TLC/QLC/etc. This allows one to divide the array into high-reliability versus high-capacity regions.

There are also expensive high-grade SLC NAND flash chips available that offer significantly higher retention time than the cheaper commodity channel TLC NAND (i.e. 10 years versus 3 years).

In general, though, whether NAND or NOR, the fundamental way that flash works is by creating an isolated voltage charge for each bit (or several bits, for TLC), making it effectively a vast grid of very tiny batteries.

Like all batteries, no matter how well-stored, they will eventually leak energy to the point where the voltage levels change enough to matter.

Further, it's not enough to simply make power available to this grid since the refresh of the cells requires active management by a nand controller chip and its associated software stack.