Sure the mom down the street who wants to blog about the her kitchen recipes wont be needing it, but a lot of websites "do"
Sure the mom down the street who wants to blog about the her kitchen recipes wont be needing it, but a lot of websites "do"
The issue is what people are choosing to do with the tools, not the tools themselves.
[0] For example something like https://github.com/xuset/planktos but without the JavaScript.
Except that the current trend in webdev is to deploy small incremental changes multiple times per day and cache-bust the assets that change on each of those deploys. So the user is probably actually downloading the JS asset at least once per day Monday through Thursday (because no deploys on Fridays).
I cannot remember how many times I have visited SPA websites that break the browser url history.
Also, if a SPA fails to load a request for any reason, try reloading it. Ops you start over.
And I am not talking about some people that don't know what they are doing. At times I've had issues with Google's new developer console, gsuite admin, analytics, product hunt and others.
Evangelists of bad technologies always like to trott out the nonsense about "a good carpenter never blames their tools"... well of course they don't: they buy the tools and always buy the appropriate ones. Further, if they did complain the customer would wonder why they bought bad tools in the first place.
A carpenter would never try to build a building with a "JavaScript" equivalent in the first place. They recognize the tool as garbage (perhaps after trying, and failing, to use it) and switch to something more appropriate.
And if you need a diagraming tool, maybe a website isn't the best solution.