Certificate expiration timeline...

You should be able to rotate the certificate on the device; this is not a major technical challenge.

Local hubs solve that pretty well, aside from still needing to update the hub.

Cool. Now go check out Mojo.

> Cool. Now go check out Mojo.

https://docs.modular.com/mojo/vision

Have you been using it? What for? What's your verdict so far?

I've been mildly interested, but the way they intertwine positioning with Modular platform makes me wary of platform lock-in.

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

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.

The submission process is pretty trivial too - as long as your code gets a PR review, and is given the green light to be merged into trunk (which is the 99% case, even if there are PR comments to address), it's going to be in the next daily build.

The releases are the things that are few and far between - generally though, a nominated daily-build (based on the pre-determined release schedule) is triaged and tested by QA and engineering for a while before release, and then ... it's out there...

...Unless something goes unexpectedly wrong with the nomination, anyway. That's pretty rare because builds are constantly being made, regressions identified, and new bugs discovered and earmarked as "must-fix" (or whatever) on a daily basis. B&I have a fairly good feel for how things are going at any given time.

It's really just timing. If you can squeeze another fix in before the cutoff deadline for the nominated build, you're in. If not, you wait until the next one, which can be a while...

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.

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.

that is just one step from Floppotron...

https://silent.org.pl/home/2022/06/13/the-floppotron-3-0/

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?

It never went anywhere.

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