That's not exactly how I would summarize the current moment in time.
This OP article doesn't really go into it, but they did actually propose a solution to the divide, they just needed more time to develop it. The Reuters article is reporting on one person's response to the proceedings, which involve more details than this particular article covers.
For instance:
> To address those concerns, Apple designed a system called Trusted System Agent, an intermediary that would let competing virtual assistants safely access the same features and capabilities as Siri AI on EU devices. Apple also proposed launching Siri AI in Europe while rolling out the Trusted System Agent gradually over 18 months. The European Commission rejected both proposals, and according to Apple, did not agree to any alternative.
That only reinforces my argument. Apple could have waited, but they decided to go ahead now and bring it to the EU later when they can address the concerns. That's great, that's the law working.
I'm glad I've been sitting on my iPhone 15 Pro Max... I'll upgrade someday, if/when I need to and the software updates are compelling, but I'll see how things run on my M5 Macbook. But the 15 Pro Max isn't subpar in any other way.
That's the thing that jumped out to me here—iPhones themselves and everything you could actually do with one during that period were way different from today. There were effectively no endless feeds of content to consume, the phone screens were way smaller and less vibrant, push notifications only came out about halfway through.
I was age 19-23 during that period (in the "highest impact" age group from the article), and I think I used my phone more for coordinating in-person social activity than anything else at the time. Additionally on that—iPhones were not widespread in my cohort at the time, even at an expensive private college with many students from upper income families.
It really did start in the time frame. Facebook opened in 2006. Twitter already existed and grew rapidly in that period. There were messengers. And because everything was slow, I suppose it could even take an hour to doom scroll Slashdot.
I’m a solopreneur working on a fairly large number of independent projects.
I use Claude Code to initiate a project using Sahil’s ME skill pack and write a high-level spec to a Linear ticket. If/when I’m ready to work on that idea, I convert it to a project, decompose the top ticket into more issues. I also have Claude code add to each issue with deepseek, sonnet or opus tags based on which is most appropriate for the issue.
Then I fire up opencode and go through each ticket. Plan, then build. Every N issues I switch to opus and have it review the work done.
Enhancements and bug reports get filed in the project. Repeat as necessary. I work pretty sequentially. I’m quite happy with the operational success of my projects. They’re all being used.
I’ve expanded this process a few times but this baseline is where things shrink to. Sometimes I use open chamber but opencode cli works for me.
This won't replace commercially viable, revenue generating alternatives of their own devising, but it does enable development activity and initiate conversations with enterprises who start with this model but want to do slightly more.
That's my experience right now... my company is all in on a plethora of platform products. Also, Microsoft just yesterday said their goal was "Unmetered intelligence". There's a lot of things that can be enabled by small local models, and those things are part of stacks that can generate revenue in other layers.
reply