Comment on How JavaScript Overuse Ruined the Web
balder1991@lemmy.world 4 weeks ago
I mean, this post makes no valid argument against JavaScript, there’s no benchmarks or anything aside from an opinion.
I don’t personally like webdev and don’t like to code in JavaScript, but there are good and bad web applications out there, just like any software.
A single page can send out hundreds or even thousands of API requests just to load, eating up CPU and RAM.
The author seems to know the real problem, so I don’t know why they’re blaming it on JavaScript.
LodeMike@lemmy.today 4 weeks ago
Because only JS is able to do that. Everything else is just a dependency tree.
watty@lemm.ee 4 weeks ago
That’s not necessarily special to JS. It’s special to client-side code. A mobile app writing in swift could do this. A cli tool written in any language could do this.
This isn’t an argument against JS, it’s an argument against misuse of client hardware.
LodeMike@lemmy.today 4 weeks ago
edited my comment to include the excruciatingly obvious assumption.
towerful@programming.dev 4 weeks ago
A page could load thousands of images and thousands of tiny CSS files.
None of that is JS, all of that is loads of extra requests.
Never mind WASM. It’s a portable compiled binary that runs on the browser. Code that in c#, rust, python, whatever.
So no, JS is not the only way to poorly implement API requests.
Besides, http/2 has connection reuse. If the IP and the TLS cert authority is the same, additional API/file etc requests will happen over the established TLS connection, reducing the overhead of establishing a secure connection.
Your dislike is of badly made websites and the prevalence of the browser being a common execution framework, and is wrongly directed at JS.