Our personal devices are far from thin clients.
Our personal devices are far from thin clients.
I think it depends on if you see the browser for content or as a runtime environment.
Maybe it depends on the application architecture...? I.e., a compute-heavy WASM SPA at one end vs a server-rendered website.
Or is it an objective measure?
The text content of a weather app is trivial compared to the UI.
Same with many web pages.
Desktop apps use local compute, but that's more a limitation of latency and network bandwidth than any fundamental need to keep things local.
Security and privacy also matter to some people. But not to most.
Turn off internet on they iPad and see how many apps that people use still work.
The Ipad is a high performance computer, not just because Apple think that's fun, but out of necessity given its ambition: the applications people use on it require local storage and rather heavy local computation. The web browser standards if nothing else have pretty much guaranteed that the age of thin clients is over: a client needs to supply a significant amount of computational resources and storage to use the web generally. Not even Chromebooks will practically be anything less than rich clients.
Going back to the original topic (and source of the analogy), IOS hosts an on-device large language model.
Maybe a PC without a hard drive (PXE the OS), but if it has storage and can install software, its not dumb.