any plans to make 1m context standard for codex/gpt 5.x subs as anthropic has with cc and opus for subs? 258k toks is sometimes a little tight, even 500k would help.
It does, I agree. That said, they've published some Apple Research docs/papers & core documentation where they outline the architecture and how it works. Personally I think their approach is fascinating.
Yep. Google doing Google things. Not everyone stays and just keeps using them though, we're actively planning to remove GCP from our primary workloads now and will cut our spend to about 1/10 of current as we keep them in the stack as a cold multi-cloud failover target only.
Excellent take. Had Apple made a dummy proof "Pass" portal for clubs, venues, etc to use to visually design and manage passes (and maybe even distribute?) when they launched this, I think it would have exploded, and the ecosystem lock in would have just been all that much deeper. But Apple doesn't really think or operate like that.
Be really interesting to see how their approach evolves over the next couple years with sea changes happening all around them in this moment.
You are correct on both accounts, as of tahoe 26.3 you can't nest a macOS guest under a macOS guest. However you can nest 2 layers deep with any combo of layer 1 guest so long as the machine is running Sequoia and is M3/M4/M5.
I live about 3 miles out of town, fortunately directly on a rail trail. I ride my e-bike in to town to get groceries weekly. I have saddlebags on the bike and I pull a kids trailer with the seat folded down and have never run out of room, or had issues with weight. Sometimes I'll even get a few bags of water softener salt. I have a fat tire ebike (aventon), it's pretty sturdy. I've got about 2k miles on the bike, I'd guess half those are from grocery runs.
I’m not a turn spotlight off guy but it is a bit of a pig in terms of apple’s approaches to system crawling and indexing and how it leaves its metadata detritus all over the disk. I can see the desire to disable it for some.
Challenge with trying to use Raycast more broadly in lieu of Spotlight for systemwide search is Raycast appears to be built on top of the spotlight indexes (mds mdworker)
I am with you in that this rhetoric is getting exhausting.
In this particular case though I don't think "evil” is a moral claim, more shorthand for cost externalizing behavior. Hammering expensive dynamic endpoints with millions of unique requests isn’t neutral automation, it's degrading a shared public resource. Call it evil, antisocial, or extractive, the outcome is the same.
This is the “answer” in plain sight and I agree. The iPhone is the beating heart of the modern Apple empire. Tim Cook has been a vocal proponent of AR since the summer of Pokemon Go. That combined with Meta getting traction with their Rayban line is almost certainly at the center of an overarching internal strategy at Apple to ensure they are positioned to maintain or even grow position as end user mobile computing form factors shift beyond the traditional smartphone. Getting the ux and app ecosystem ready visually is what ‘caused’ Liquid Glass.
