probably niche, but we have an m4 iMac mounted to a built in desk in our kitchen. my family of 4 all have MacBooks, but the iMac gets heavy usage by all of us. kids will sit and do homework there, wife adds things to her grocery list, keeps her personal mailbox clean, does basic household web tasks. I use it to do household tech chore work, pay bills, etc when everybody is hanging around the kitchen. We all use our computers too, but the convenience factor of it's already on, powered, connected and ready to go is a draw and leads us to magnetize to it when we need it. I love it the most as I think it keeps us present with each other vs going off to a private space to do those sorts of things. Yeah we could just as easily drag our laptops into the kitchen but then you end up finding a comfy spot on the couch or for the kids in their rooms.
> Yeah we could just as easily drag our laptops into the kitchen but then you end up finding a comfy spot on the couch or for the kids in their rooms.
I've been feeling that: much about keeping my sanity in this age is about noticing those patterns we keep falling in and arranging for "easier" ways to fall into healthier patterns. The annoying thing is that it doesn't seem that those "unhealthy" patterns were that easy to predict in order to avoid. Like some 15 years ago would it have been as obvious that we would get to such a consistently predictable pattern of "comfy spot on the couch or bed" and the unhealthy social and personal repercussions of that?
I just wish I start being able to predict those pitfalls earlier than the current few years per tech evolution.
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.
reply