How the Unix philosophy gave us “web apps” instead of “software”
capiche.com
capiche.com
Looks like author mentioned that. I guess, the change is in the name - and perception.
It's a little tedious to set up, but no code has to be written.
To be fair, I think the microservice architecture addresses this idea on the web. Moving towards smaller interoperable pieces is something that the internet has been doing for a bit Imo
The fact that (some) web apps transmit data via an API, which is text, doesn’t mean that text is their primary interface.
Also, what web application does just one thing today? The most popular ones are absolute seas of features. Unix commands also became fairly poor at sticking to this, but nowhere near to the level of web apps.
The web was simply a working cross-platform and usable over the network environment despite the bad performance, additional hardware (connectivity) requirements and developers found these advantages significant enough to prefer building web-apps over desktop equivalents. Unfortunately, because major websites are still a PITA to use and [would] greatly benefit from native implementations (FB, Twitter, Youtube...).
As for webapps, they have nothing to do with unix philosophy and much more to do with Steve Jobs, iphone apps and too many non technical product managers angling to push out “products” (also an aspect of the whole MVP and ship early mentality)
The market shows that people like free stuff and cheap little programs ('exercise workout timer on your iphone') but will pay for a zillion features (AutoCAD, Lightroom, Tableau, the AWS ecosystem are examples).
Even the variants of Unix tools with a lot of features seem to have won in the marketplace of ideas.