Back in the early ‘70s, I worked at a computer network that had remote clients up and doen the Eastern seabboard, from Maine to D.C. They used a circular buffer for output from client submitted jobs. One day the buffer lapped itself. Panic ensued.
Apple and Google have said that Private Cloud Compute will be involved as well, which Apple is trying to build a mystique of "on-device-like" trust. (Which yes, if Private Cloud Compute is involved and is secure in the ways that Apple says it is does presumably imply that the announced deal with Google includes selling Apple the complete model weights.)
If you pay attention to the cursor, instead of aiming at the corner of the window, the UI gives you great feedback of where you should click: when the cursor changes to 2 arrowheads pointing diagonally or orthagonally to the window, resizing is available. Why aim for inside the window? I do think the expanded corner radius of Tahoe sucks badly.
Compilers only obtained that level of trust through huge amounts of testing and deterministic execution. You don't look at compiler output because it's nearly always correct. People find compiler bugs horrifying for that reason.
LLMs are far from being as trustworthy as compilers.
If I use the same codebase and the same compiler version and the same compiler flags over and over again to produce a binary, I expect the binary to be the deterministically be the same machine code. I would not expect that from an LLM.
Recent moves have convinced me that Apple is getting ready to push Vision Pro substantially harder.
In recent weeks, I’ve been getting push notifications about VP.
They hired Alex Lindsay for a position in Developer Relations.
And there’s the M5 update.
Just remember, it’s a lot cheaper than the original Mac(inflation adjusted). Give it 40 years – hell, given the speed of change in tech these days, it won’t even take 10.
reply