Those are no longer useful as a "public square" because of the increasingly walled garden design.

Client-side algorithmic feed fixes a lot of that, it's not a fundamental flaw.

One "fix" is for the caller to correctly classify those fundamentally impossible tasks and pass them to a subprocess.

Some future "AI" could be a billion benchmark-hacks and a way to tell which one is needed.

I mean, for what it's worth, when I need to multiply two numbers, I mentally call the "multiply numbers" algorithm stored in my head, then sit down and work through the process on paper.

I've got no problem with an AI doing something similar

No need to give distant examples - the US train boom used the same strategy.

Did it? I always assumed the US train boom aligned with shipping companies more than land at the destinations, which is why even today cargo gets priority over Amtrak.

Outside of the Eastern part of the US, the railroad land grant programs were a major part.

https://en.wikipedia.org/wiki/Railroad_land_grants_in_the_Un...

This is a part of why there were so many tiny little towns out West which were essentially just a railroad stop and a few buildings.

the US train boom is much further away.

you can get to hong kong or jspan in hours to days. the train boom is about a century away

Sound Transit still uses this strategy in Seattle region.

They really don't. They don't build residential or commercial property.

If one user makes the mistake, it would be fair to blame them.

Because thousands of users make the same mistake, blame needs to be directed at Windows UX.

MS could fix this easily by 1) moving Run to optional features and 2) removing online features from Start to make performance comparable.

The other "run" interfaces (terminal, conhost, Powershell) are sufficiently menacing to scare away non-devs already.