Re:Rendering on the Web
by RobertRoberts on Monday August 19, 2019 @11:42PM
(#20743650)
I agree with you. But the problem is web designer clients _demand_ all the darn garbage on their site.
I have the scars to prove it... currently dying on said hill.
Hang in there.
A fun thought experiment: how would you go about incentivizing the clients who hire web developers to create fast loading pages but still have Javascript functionality? More importantly, who is in a position to incentivize clients who care more about tracking and marketing than performance?
Google has been factoring load times heavily into their search rankings for a while now. While I don't agree with a lot of their priorities, this gives a designer who's so inclined a lot of opportunity for encouraging clients to do the right thing: just show them their site's PageSpeed results, and they'll sober up.
Re:Rendering on the Web
by chubbyrabbit on Monday August 19, 2019 @09:11PM
(#20743059)
I get your point but it's like saying all of today's problems in the world are due to humankind.
I don't think anyone would fight you on that.
ALL (all) of the problems they face are either self-inflicted or due to other web developers, such as those who design web advertisements or bloated JavaScript libraries. The problems with sending multiple simultaneous streams to a browser are due to web developers deciding to design a web page with hundreds of individual files to be downloaded. Rendering times are long because of the complexity that today's sites are built to attain.
I can view simple sites EXTREMELY quickly today -- that is to say, sites that designers have not "improved" to the point that the site is no longer worth visiting. A simple page shows me what I want to see, and doesn't take a designer 400 hours to come up with.
All of today's problems on the web are due to web developers.
I'll fight and die on this hill, and no amount of downvotes will change my mind about this in the slightest.