zhyder

So except for Tesla, which sends lots of telemetry regardless, other manufacturers send little if you don't use their companion apps. The companion apps already seemed excessive to me; even more reason to kick them to the curb.

AI dramatically reduces the cost of writing code (especially when you have a reference), so the scale between native and cross-platform is going to tilt more towards native now compared to before.

But I'm curious what their update will be in a year or two. Because these costs don't reduce as dramatically with AI (unless you fully give up control and vibe code it):

1. Reading code

2. Manually testing code

A big part of this announcement does seem to be _delegation_ in the background; they give the example of web search but that could be any tool. I haven't tried it yet either but sounds like they've found a reasonable UX that mixes that sort of high-and-variable latency tool calling (potentially with agentic loops) with a continuously speaking live voice.

Aside from the issue of platform owners (Apple, Google, Microsoft) offering storage sync as an integrated feature, which others have pointed out, the other reason growth is limited is that filesystem storage and sync thereof has become less critical over time. Our apps increasingly do cloud-native walled-garden storage: docs in Google Docs / Notion / Confluence, mocks in Figma, etc. And code was cloud-native with version control much earlier.

I need sync for just photos on my phone (which Apple or Google are better for), and a small number of esigned PDFs and tax documents (for which any provider's free tier suffices).

Dropbox solved a problem of the 2010s.

Looks like the best display you can get in laptops at this price: 2408x1506 resolution, 500 nits, antireflective coating (!). And bonus points for no silly notch.

I guess it could warn about it but the VM sandbox is the best part of Cowork. The sandbox itself is necessary to balance the power you get with generating code (that's hidden-to-user) with the security you need for non-technical users. I'd go even further and make user grant host filesystem access only to specific folders, and warn about anything with write access: can think of lots of easy-to-use UIs for this.

Agree, can't wait for updates to the diffusion model.

Could be useful for planning too, given its tendency to think big picture first. Even if it's just an additional subagent to double-check with an "off the top off your head" or "don't think, share first thought" type of question. More generally would like to see how sequencing autoregressive thinking with diffusion over multiple steps might help with better overall thinking.

Surprisingly big jump in ARC-AGI-2 from 31% to 77%, guess there's some RLHF focused on the benchmark given it was previously far behind the competition and is now ahead.

Apart from that, the usual predictable gains in coding. Still is a great sweet-spot for performance, speed and cost. Need to hack Claude Code to use their agentic logic+prompts but use Gemini models.

I wish Google also updated Flash-lite to 3.0+, would like to use that for the Explore subagent (which Claude Code uses Haiku for). These subagents seem to be Claude Code's strength over Gemini CLI, which still has them only in experimental mode and doesn't have read-only ones like Explore.

"the value of a human eyeball" / attention is and always will be the limited resource. But I wish the way the economy worked wasn't that attention is sold for money, which makes money the moat, and sets a floor on how low-priced things can get for customers too. Is this really the best the economy can do? Or is it possible to have a fair LLM-based search engine that matches customer need description with stated product descriptions from providers (while weighing customer reviews, etc)?

Hmm the whole point of checkpoints seems to be to reduce token waste by saving repeat thinking work. But wouldn't trying to pull N checkpoints into context of the N+1 task be MUCH more expensive? It's at odds with the current practice of clearing context regularly to save on input tokens. Even subagents (which I think are the real superpower that Claude Code has over Gemini CLI for now) by their nature get spawned with fresh near-empty context.

Token costs aside, arguably fresh context is also better at problem solving. When it was just me coding by hand, I didn't save all my intermediate thinking work anywhere: instead thinking afresh when a similar problem came up later helped in coming up with better solutions. I did occasionally save my thinking in design docs, but the equivalent to that is CLAUDE.md and similar human-reviewed markdown saved at explicit -umm- checkpoints.