Can we blame Javascript for the current bloated web experience?

>>57207303
No, we have to blame shitty developers.

>>57207303
No, we have to blame overuse of JS in tasks where it's not intended to be.

>>57207303

javascript isn't the problem, proper javascript done correctly can shave a ton of time off of page loading times and anyone who doesn't believe this has clearly never used the web pre-2005 ish

the problem, as always, is the shitty dodgy advertising companies that moved away from god awful flash ads to image/html5 video coupled with javascript ads with the web developers wanting to get in on the selling user data craze for pennies more per 100,000 views and implementing 5 different analytic gatherers, load balancers, offloading js development by using (((free))) libraries that are hosted off site to further scrape as much userdatas as they can

note that sites that don't do any of these shitty advertising/analytic practices that are heavy on javascript work fine

>>57207303

Who is doing "pure" JavaScript nowadays?
There's CoffeScript, TypeScript, Dart..

Also the "bloated web experience" is exactly what the stupid Millenials want. Blame them.

>>57207980
/Thread

>>57208131
Millenials is the auditory of this site, anon.

>>57208131
Most of the JS alternatives offer so little utility over normal JS that the hassle of setting up a build pipeline and getting other libraries to work with it just isn't worth the time for most projects.

TypeScript is goat for big projects though.

>>57207303
>left-pad
yes

When will webassembly become common?

>>57207980
this

blame the shitty devs who do it, the shitty UX people who think everything needs to be over-engineered instead of slim and efficient, the shitty smartphone generation people who like it that way because they dont know any better, the shitty corporate world for taking anything bad and inflating it, and the stupid bootcamp people who think everyone should be a programmer because "anyone can learn it in a day"