Because it was a profit making venture for car companies. Suburbs are horrifically inefficient, they survive by the twisted "communism" of cannibalizing the dense urban tax bases to support the sprawling, expensive to service and maintain, isolating flatlands.

My initial motivation for this was the "account 89% full" notice, so I wanted to delete all the old junk to free up some space. But after reviewing what's in there (and I've had that account since ~2004) the opposite sentiment arose: delete everything important, unique, personal. Leave them with the junkyard of various subscriptions, newsletters, just the digital flotsam that's both ambiguous and meaningless -- perfect for appearing both legitimate and irrelevant.

Acquiescing to (however veiled and excused) authoritarian overreach is not the way forward. The correct attitude towards this "Think of the Children but Really Think of the Advertisers' Profits" initiative is to let California (and other proponents) to figure out how they can do business without Linux or any other software that depends on it.

OSS is a bastion of freedom -- real freedom, freedom FROM, not American Freedom (freedom to abuse and exploit others). We must defend it. DO NOT COMPLY.

OP, what have you used this on in practice, with success?

CLI tools have an edge in that their definition live in model weights; MCP requires a portion of the context for tool definitions.

Having an extra server just to orchestrate the tools, I don't like it.

For anything that does not have a native CLI tool -- just write a wrapper, a shell script, whatever performs the task adequately. It folds into the workflow nicely. Leveraging decades of unix tooling philosophy has its benefits.

Having a shell runner is just... simpler. And as another comment mentions, you can create users for the various agents to restrict their access to things, almost as if that's what users were meant for!

Neither can they be easily searched nor organized. And what prolonged AI use teaches you is: don't search for that old chat, just ask anew.

That particular piece of flypaper isn't as sticky as it may seem.

So yeah, I believe "it's a phase" but in a sense that it's a development phase, just like planning or prototyping.

I think it's more along the lines of acknowledging the fast-paced changes in the field, and refusing to cast into code something that's likely to rapidly evolve in the near future.

Once things settle down into tested practices, we'll see more "permanent" instrumentation arise.

It doesn't take much to throw in a LTE modem, sim card reader, a mic and a speaker -- suddenly you have a phone!

I'm don't really have a point here, and I don't know exactly where my meandering project will eventually end up -- but I really like the "own the full stack" aspect of it, and the decoupling of my little device from all the extras that have accumulated under the umbrella of "phone".