You must log in or register to comment.
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.
Because only JS is able to do that in a web browser. Everything else is just a dependency tree.
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 resources.
edited my comment to include the excruciatingly obvious assumption.
Seems like you read the first two sentences of my post and stopped there, so you completely missed the point.
It’s not JS that is the problem. It’s an issue of client resource use. That would be true no matter what language is being used.
Not necessarily. Programmers are heavily influenced by the language they use. There’s a reason there’s so many JS frameworks.
Article is correct but kind of low effort. Web slow from too much JS and self serving framework vendors, got it.
Most of the web now is like that article.
AI has a role in turning pages and pages of text into one sentence.