Technology

75963 readers

4369 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related news or articles.
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, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
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

L3s@lemmy.world

enu@lemmy.world

technopagan@lemmy.world

L4s@lemmy.world

L3s@hackingne.ws

L4s@hackingne.ws

177

How JavaScript Overuse Ruined the Web (donald.cat)

submitted 8 months ago by columbus@lemmy.world to c/technology@lemmy.world

42 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] balder1991@lemmy.world 39 points 8 months ago (6 children)

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 0 points 8 months ago* (last edited 8 months ago) (5 children)

Because only JS is able to do that in a web browser. Everything else is just a dependency tree.

[–] towerful@programming.dev 3 points 8 months 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.

load more comments (4 replies)