this post was submitted on 04 Feb 2025
180 points (90.9% liked)
Technology
61774 readers
3672 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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.
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.
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.