JavaScript broke the web (and called it progress) - Jono Alderson
Technology
21
Beiträge
14
Kommentatoren
21
Aufrufe
-
This post did not contain any content.
JavaScript broke the web (and called it progress)
We replaced simple websites with complex apps nobody asked for. Now it takes a complex build pipeline just to change a headline.
Jono Alderson (www.jonoalderson.com)
Hey, I've read exactly the same article 15 years ago, but back then it was Flash that "broke the web".
-
Client-side scripting is a hack. HTML didn't have all the tags people wanted or needed, so instead of carefully updating it to include new features, they demanded that browsers just execute arbitrary code on the user's computer, and with that comes security vulnerabilities, excessive bandwidth use and a barrier-to-entry that makes it difficult to develop new browsers, giving one company a near-monopoly.
I've read it wasn't a hack, but my memory is mixed and I'm as old as JavaScript.
It was somewhat of a consensus that scriptability is needed. Java applets, Flash, Sun plans to add support for scripting webpages with Java, alternative plans for the same with TCL, Netscape plans for the same with some Lisp, and then they decided upon what became JS.
A lot of things are scriptable and it is convenient. I'm not sure anyone expected this to be just used as a base for more and more complexity in an application platform. Probably the idea was that scripted hypertext pages will remain such, and in future there will be other dedicated technologies for other purposes.
I'm fascinated with Java, just can't concentrate on learning it. My idea of a wonder language would run on something like JVM (or like Forth machine, LOL) and be as terse and simple as TCL.
-
Hey, I've read exactly the same article 15 years ago, but back then it was Flash that "broke the web".
and we got rid of it.
-
Hey, I've read exactly the same article 15 years ago, but back then it was Flash that "broke the web".
Flash never got in the way the same like js. My main take from the whole piece is how it has changed the way websites are developed, to match that of traditional software development. Like the need to deploy to change some text in the footer of our website
-
Oh yeah, it's totally JavaScript that's the reason that news and magazine websites suck. It's totally not the financial incentives of advertising that cause them to only care about the user experience so far as they get clicks. This totally wouldn't have been the exact same result if new media did everything on the backend and underfunded their backend dev teams. /S
Jesus Christ, why do these inane articles keep coming up? The authors have the reasoning skills of "when I look into the sun my eyes hurt, therefor the sun is bad".
- SEO consultant
- AI hero image
Wonders why the web is shit
-
and we got rid of it.
And the web has gotten shittier everyday
Since -
Flash never got in the way the same like js. My main take from the whole piece is how it has changed the way websites are developed, to match that of traditional software development. Like the need to deploy to change some text in the footer of our website
Ow my dear, you never used flash did you? We didn't even have 'deploys' back then, we needed to re-upload the entire container file, to change some text in the footer
-
Ow my dear, you never used flash did you? We didn't even have 'deploys' back then, we needed to re-upload the entire container file, to change some text in the footer
No - I never coded complete websites in flash. But if I did my «upload of the whole container» would have been my deployment
-
No - I never coded complete websites in flash. But if I did my «upload of the whole container» would have been my deployment
You are correct, but missing the point.
-
You are correct, but missing the point.
Nah. im right on target, but thanks for the great insights
-
Oh yeah, it's totally JavaScript that's the reason that news and magazine websites suck. It's totally not the financial incentives of advertising that cause them to only care about the user experience so far as they get clicks. This totally wouldn't have been the exact same result if new media did everything on the backend and underfunded their backend dev teams. /S
Jesus Christ, why do these inane articles keep coming up? The authors have the reasoning skills of "when I look into the sun my eyes hurt, therefor the sun is bad".
To be fair, there are a lot of inane articles saying this exact same thing about javascript. If its true, its ancient history, and I'm tired of it. I learned javascript when it was a babe, and watched many other platforms fall by the wayside. I'm not defending anything about it, but javascript works. Still.
-
Nah. im right on target, but thanks for the great insights
Why did you think I put 'deploy' in quote then?
-
Client-side scripting is a hack. HTML didn't have all the tags people wanted or needed, so instead of carefully updating it to include new features, they demanded that browsers just execute arbitrary code on the user's computer, and with that comes security vulnerabilities, excessive bandwidth use and a barrier-to-entry that makes it difficult to develop new browsers, giving one company a near-monopoly.
Wanted, maybe, but needed? It even had marquee, what else could anyone need?
-
Flash never got in the way the same like js. My main take from the whole piece is how it has changed the way websites are developed, to match that of traditional software development. Like the need to deploy to change some text in the footer of our website
I disagree. flash popup ads were fucking horrendous.
that said, flash was poisonous. js is venomous.
-
I disagree. flash popup ads were fucking horrendous.
that said, flash was poisonous. js is venomous.
I was referring to how it affected website development, not UX.
From my understanding of the article the author has noting against js, just how it affects the development process and architecture choices.
