dyld[71398]: Library not loaded: /System/Library/Frameworks/FoundationModels.framework/Versions/A/FoundationModels
Referenced from: <32818E2F-CB45-3506-A35B-AAF8BDDFFFCE> /opt/homebrew/Cellar/apfel/0.6.25/bin/apfel (built for macOS 26.0 which is newer than running OS)
Reason: tried: '/System/Library/Frameworks/FoundationModels.framework/Versions/A/FoundationModels' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/System/Library/Frameworks/FoundationModels.framework/Versions/A/FoundationModels' (no such file), '/System/Library/Frameworks/FoundationModels.framework/Versions/A/FoundationModels' (no such file, not in dyld cache)
MacBook Neo forced me to finally make the jump, and it turns out that I, much like the engineers at Apple, don't really care about the spit and finish anymore. Third-party applications handle everything else. Also, I was happy to find that Divvy still runs just fine under Rosetta.
The upper arm of the K shaped economy uses their capital to invent and control the replicator and the lower arm dies off? Seems like the most realistic path to "post-scarcity" from where we're standing now.
Still an amazing hack today and I love it. However, I heard Apple are developing a touch screen MacBook this year, and I simply don't get why they're doing that. I don't know what's worse, the ergonomics or the fingerprints.
I have been around touch screen Windows laptops for I don’t know how many years now, and I have never felt even the slightest compulsion to touch the screen.
It might be a generational thing; my kids get touchscreen laptops from their school, and they interact with them almost exclusively by touching the screen. I agree, I'd much rather use a mouse (or even better, a trackball; i wish most laptops still had those)
Good work. I'm happy to see this for Redox. There are numerous implementations of capabilities now, and they confirm that the concept really does simplify access control and sandboxing.
But the platform has used caps internally all along. Cloudflare makes heavy use of Cap'n Proto (https://capnproto.org/), a capability-based RPC protocol, and recently released Cap'n Web (https://capnweb.dev/), a JavaScript-oriented version of the same idea. The "Cap'n" in both is short for "Capabilities and". (Dynamic Workers sandboxing is based around Cap'n Web capabilities.)
Most successful sandboxes use capabilities, though it's not often something you hear about. Android's IPC system, Binder, is a capability system. And Chrome has a capability-based IPC system called "Mojo".
Implementations include seL4, Barrelfish, Google Fuchsia OS, Capsicum, and a slew of research systems too long to list. It's also worth checking out tangential things like the E programming language and Google's old Caja project.
I also miss the all-capitals ARM spelling. I think they've never been the same since they've changed that, since around the same time their business strategy went from sensible to nonsense.
Not in British English, is my point. Look for example on the BBC, it's written "Nasa". I'm not saying I agree with it, but it's something you learn living in UK and former commonwealth countries.
The BBC (all caps) style guide splits the treatment of acronyms; BBC is all caps as it is spoken as a series of letters Bee Bee Cee.
Nasa is spoken as a single word.
From the BBC:
Use the abbreviated form of a title without explanation only if there is no chance of any misunderstanding (eg UN, Nato, IRA, BBC). Otherwise, spell it out in full at first reference, or introduce a label (eg the public sector union Unite).
Where you would normally pronounce the abbreviation as a string of letters - an initialism - use all capitals with no full stops or spaces (eg FA, UNHCR). However, our style is to use lower case with an initial cap for acronyms where you would normally pronounce the set of letters as a word (eg Maga, Sars, Aids, Nasa, Opec, Apec).
The ABC Australia style guide is a hot mess (first examples: Quantas TAFE modem are inconsistent "spoken words" and other issues) ... I'm wondering if it was last edited by an LLM or young intern.
There are two versions of MPK. One is only applicable to userspace pages. The other is newer and can be applied to kernel space pages; last time I checked, this was only available on newer Xeon processors.
By the way, MPK memory is not encrypted. The key is just an identifier for the requestor. If the requestor key doesn’t match the same identifier for the memory page, then an exception is raised.
Funnily enough, MPK isn’t new at all. It’s almost a reintroduction of a feature from Itanium.
Aw, so I was half right. I knew the newer one, which is MPS, will throw a page fault. Sorry, it’s been a while since I’ve done this stuff and we were mostly working with tz
It shouldn't be a struggle. If you need colour quality (e.g. content creation/consumption) get the Studio Display. If you need real estate (e.g. technical work or programming) get the Kuycon.
reply