That "what if" cost is going to be built into the cost of the laptop. Repairability doesn't always keep the cost low. The purchaser will definitely have to foot the cost otherwise it isn't sustainable.

Yes, the site is new, but other posted articles are 100% consistent with the author wanting a guaranteed level of local inference with large models.

What I read was written by a skeptic who took claims and systematically addressed a number of issues. The debunking was concise and used simple sentences.

The boxes in the pictures were, to my eyes, generated manually using the macOS Preview annotation feature. They are not well aligned. I've used this technique many times to general overlays. If this were me, I'd get called out. I like nicely spaced and proportioned boxes! NB: iFixit tear downs are mis-aligned as well and it bugs me.

People have a distasteful habit of assigning others into boxes. Particularly if that box currently has a negative connotation. Boxing is a primary tool of the; misguided, bullies, sycophants, censors and those with an unspoken agenda. Humor: Which box applies?

[1] a GUI app can restore access to files by using a trusted external selection process.

Edit: change footnote reference to prevent markup error.

If you are using "sandbox-exec" then you are likely maintaining your own seatbelt profile. Keeping those up to date can be challenging, especially for 3rd parties as any changes to underlying Frameworks and libraries can break a hand crafted profile.

If you are using it to secure your own stuff and accept this and not complain, even for minor SW updates, then you are going to be fine. Don't ship things to 3rd parties without also accepting this. That is what this deprecated means.

There was another device between the BBC Micro and the "Versa Braille" unit. The interposing unit was a matrix switch that could multiplex between different serial devices - I now suspect it might also have been doing some character escaping / translation.

For those not familiar with Braille, it uses a 2x3 array (6 bits) to encode everything. The "standard" (ahem, by country) Braille encodings are super-sub-optimal for pretty much any programming language or mathematics.

After a bit of (me)memory refresh, in "standard" Braille you only get ( and ) - and they both encode to the same 2x3 pattern! So in Braille ()() and (()) would "read" as the same thing.

I now understand why you were asking about the software used. I do not recall how we completely worked this out. We had to have added some sort of convention for scoping.

I now also remember that the Braille terminal aggressively compressed whitespace. My friend liked to use (physical) touch to build a picture, but it was not easy to send spatial / line-by-line information to the Braille terminal.

Being able to rely on spatial information has always stuck with me. It is for this reason I've always had a bias against Python, it is one of the few languages that depends on precise whitespace for statement syntax / scope.

He is still active and online and has a contact page see https://www.foneware.net. I have been a poor correspondent with him - he will not know my HN username. I will try to reach out to him.