JavaScript broke the web (and called it progress)
jonoalderson.com
JavaScript broke the web (and called it progress)
1–10 of 171 posts
Re: JavaScript broke the web (and called it progress)
#2Bitch about JavaScript all you want but this exact failure has occurred in many languages. It’s not a language failure. It’s a people failure. Nobody trains JavaScript developers properly and employers knowingly hire unqualified people to do the work. Of course the result is shit. It would be just as shitty if this were a different language.
If you want to isolate yourself from so much of the stupid then use a PiHole on your home network and stop working around JavaScript. It works for me as someone with 15 years writing JavaScript.
Re: JavaScript broke the web (and called it progress)
#3Bitch about JavaScript all you want but this exact failure has occurred in many languages. It’s not a language failure. It’s a people failure. Nobody trains JavaScript developers properly and employers knowingly hire unqualified people to do the work. Of course the result is shit. It would be just as shitty if this were a different language. If you want to isolate yourself from so much of the stupid then use a PiHole…
Why not learn from past failures? Then everybody gets a great user experience, not only those of us who know how to set up a pi-hole. Everybody wins! Apart from the framework-industrial complex, that is.
Re: JavaScript broke the web (and called it progress)
#4Bitch about JavaScript all you want but this exact failure has occurred in many languages. It’s not a language failure. It’s a people failure. Nobody trains JavaScript developers properly and employers knowingly hire unqualified people to do the work. Of course the result is shit. It would be just as shitty if this were a different language. If you want to isolate yourself from so much of the stupid then use a PiHole…
Agree, been working with Js (frontend only) for a few years now and never had real issues. I wouldn't chose it for my backends though...
Re: JavaScript broke the web (and called it progress)
#5That is because the actual alternatives to JS such as Flash, Silverlight and Java Applets were much worse. Native apps are bound by the platform's walled garden and practically undiscoverable, hence the need for web apps.
Re: JavaScript broke the web (and called it progress)
#6> Spoiler alert: we didn’t get app-like performance. We didn’t get better user experiences.
Not sure about that, I'll take Gmail and fastmail any day over outlook and evolution
Re: JavaScript broke the web (and called it progress)
#7Saying JS broke the web when your website loads 754kB of JS across 13 separate requests makes me wonder if you're very serious about the problem.
Re: JavaScript broke the web (and called it progress)
#8I wish that it did actually break the web so I didn't have to see this same dumbass article every two weeks
Re: JavaScript broke the web (and called it progress)
#9Bitch about JavaScript all you want but this exact failure has occurred in many languages. It’s not a language failure. It’s a people failure. Nobody trains JavaScript developers properly and employers knowingly hire unqualified people to do the work. Of course the result is shit. It would be just as shitty if this were a different language. If you want to isolate yourself from so much of the stupid then use a PiHole…
Why not learn from past failures? Then everybody gets a great user experience, not only those of us who know how to set up a pi-hole. Everybody wins! Apart from the framework-industrial complex, that is.
Well, paraphrasing Hegel, we can learn from past failures that the industry as a whole does not learn from past failures. It's just the Eternal September situation, and all we can do is tend our own gardens.
Re: JavaScript broke the web (and called it progress)
#10The problem of the web as application platform isn't mainly Javascript (just use a proper linter and/or TS, or even WASM), but the adhoc-designed web API layer stack (e.g. the 3D rendering API should sit below the DOM, and there should be a couple of medium level APIs between the low-level rendering API and the DOM (such as text- and shape-rendering, a rectangle-layout API, a compositor API and an accessibility API which then the DOM is built on top - but which could also be used on their own), also WebAudio is just bad:
https://blog.mecheye.net/2017/09/i-dont-know-who-the-web-aud...
...and don't get me started about 'trivial' things like copy-paste, fullscreen, input handling and filesystem access. These are all not programming language problems, but API design problems.
...e.g. the web could be so much more when there wouldn't be this schism between the 'document-view orthodoxy' and the 'app-platform protestants' ;)