JavaScript growth and third parties
speedcurve.com
JavaScript growth and third parties
1–10 of 77 posts
Re: JavaScript growth and third parties
#2Ironically after 47 minutes on HN their site doesn't load at all.
Here is a cached version that works: http://webcache.googleusercontent.com/search?q=cache:https:/...
Re: JavaScript growth and third parties
#3I'd rather attribute that to ads, especially terrible ones that cause page reflow, than just javascript.
Re: JavaScript growth and third parties
#4One of the big problems with JavaScript is that some developers don't know it very well (me included) but have to get some feature working, so import multiple frameworks/libraries to get their job done, most of which is not needed.
Re: JavaScript growth and third parties
#5Yeeeeeeeeeeeeees.
Re: JavaScript growth and third parties
#6EDIT: The HN title changed so I don't know if this comment is relevant anymore.
That sounds like saying "living is the leading cause of death".
I mean, I don't particularly like JS, but it seems like we decided long ago that plain documents and links won't cut it. Everything, apparently, needs to be a rich web application with huge images and a gazillion of ads.
Why is that Javascript's fault?
Re: JavaScript growth and third parties
#7I don't understand why JavaScript is so ubiquitous now. There seem to be very few cases where it is actually necessary and useful (e.g. a calculator form that does computations client side that would otherwise overwhelm the server).
I am constantly surprised at the number of sites that should be totally static (e.g. a local restaurant's menu page) that display nothing at all when I visit with JavaScript disabled.
Can someone who actually makes websites explain why this has happened? Is this about varying screen resolutions and aspect ratios in the era of phones and tablets? Can't you just use CSS instead?
Re: JavaScript growth and third parties
#8While I do acknowledge that increase in generic third-party things like ads and trackers definitely plays a certain role here isn't the study is kind of moot unless sites with similar feature sets are compared.
Re: JavaScript growth and third parties
#9O(c^n) is what makes websites slow. Piling libraries, frameworks, trackers, and other third party services on-top of each other, that each has thousands of dependencies.
Re: JavaScript growth and third parties
#10Google Mail feels like it's transmitting over a 57.6k modem these days. If developers at Google can't make fast JavaScript front ends, what are the odds that an average front end developer can?