Live data from Hacker News

The average size of Web pages is now the average size of a Doom install

mobiforge.com

281–290 of 467 posts

Re: The average size of Web pages is now the average size of a Doom install

#281

I'm skeptical that developers talking to each other about how bad web bloat is will change anything. They will still face the same incentives in terms of ad revenue, costs of optimization, etc. Here's a random idea that might have more potential: create an adblocker browser plugin that also colors URLs based on how slow they are expected to load, e.g., smoothly from blue to red. The scores could be centrally calculat…

Something that would be more effective is if Google began factoring page load speeds in their rankings just like they did for mobile optimization.

Re: The average size of Web pages is now the average size of a Doom install

#282
post #49

Earlier quoted context omitted.

I would say that a possible solution is also to better rank websites that mention the checksums of their external resources and make web browsers keep them in cache much longer... if pretty much every website uses jQuery, perhaps we should ship jQuery with the web browser?

I hear this argument a lot, and I very much disagree. Now you have browser vendors having to device which libraries are "popular" and shipping them in the initial download of the browser. It turns out that this technology already exists in a much better form. It's called cache. The problem is that almost everyone hosts their own version of jQuery. If everyone simply linked the "canonical" version of jQuery (the CDN l…

> The problem is that almost everyone hosts their own version of jQuery.

Any site that expects users to trust it with sensitive data should not be pulling in any off-site JavaScript.

As for checksumming, browser vendors don't need to pre-load popular JavaScript libraries (though they might choose to do so, especially if they already ship those libraries for use by their extensions and UI). But checksum-based caching means the cost still only gets paid by the first site, after which the browser has the file cached no matter who references it.

Re: The average size of Web pages is now the average size of a Doom install

#283
post #106

Earlier quoted context omitted.

I see lots of websites that don't even cache static resources and use > 10 scripts and stylesheets, from a lot of different domains. Terrible.

And link the non-minified versions. (but the different domains actually helps speed up loading with http because it helps parallelise transfers.)

Domain sharding almost never makes any sense, especially on mobile, and with HTTP2 it's working against you.

http://www.mobify.com/blog/domain-sharding-bad-news-mobile-p...

Re: The average size of Web pages is now the average size of a Doom install

#284

Earlier quoted context omitted.

Well, not that adding the whole of underscore.js is reasonable, but maybe if Javascript had provided proper enumeration of their data structures earlier like all decent programming languages do, that wouldn't be an issue. To this day, you still can't enumerate an object literal, yielding each key/value pair. You still can't properly enumerate a NodeList and Object.values is still "experimental technology". I understa…

var obj = {...} // native JavaScript Object.keys(obj).forEach(function(key){ console.log('obj.', key, ' = ', obj[key]) }) // Lodash _.forEach(obj, function(value, key) { console.log('obj.', key, ' = ', value) }) Object.keys(obj) creates an array that contains the keys of the object, which makes it pretty trivial to call filter, map, reduce, etc. And getting the value from an object's key is also pretty straightforwar…

Ruby: obj.each{|k,v| ...}

Sure you can do it in JS, but calling Object.keys then forEach (in whose closure you'll still have to reference obj[key] by the way) still doesn't feel optimal.

Re: The average size of Web pages is now the average size of a Doom install

#285

Earlier quoted context omitted.

The experience may not be complex, but the software that builds and displays the experience is way more complex than the Apollo guidance computer.

The software that builds and displays the experience is the browser. Most webpages could be cut by 90% and be visually and functionally indistinguishable. For 90% of the last 10%, the functionality cut out would improve the user experience, especially on mobile.

..and the server, protocols, and language used to build that web page. It's not like a powerpoint presentation.

Re: The average size of Web pages is now the average size of a Doom install

#286
post #49

I'm skeptical that developers talking to each other about how bad web bloat is will change anything. They will still face the same incentives in terms of ad revenue, costs of optimization, etc. Here's a random idea that might have more potential: create an adblocker browser plugin that also colors URLs based on how slow they are expected to load, e.g., smoothly from blue to red. The scores could be centrally calculat…

I would say that a possible solution is also to better rank websites that mention the checksums of their external resources and make web browsers keep them in cache much longer... if pretty much every website uses jQuery, perhaps we should ship jQuery with the web browser?

Isn't this what the '.min' versions of these is for?

jquery-2.2.3.min.js is only 86KB for me. For the amount of functionality it adds, sure seems like a sweet deal.

Part of the problem (IMHO) is the growing requirement for larger, alpha-channel-using image formats like PNG, that then need to be expressed in a Retina format - I mean, shit looks terrible on my retina MacBook Pro that isn't properly Retina formatted. (Here's looking at you, Unity3D...even the current beta which supports Retina displays is extremely unstable and half the graphics (even stupid buttons on the UI) are still SD...)

With bandwidth costs declining [1] and basic RAM increasing [2] is there a particular reason a Web application should be much smaller than a typical desktop application? We have caches for a reason.

[1] http://www.networkworld.com/article/2187538/tech-primers/exp...

[2] http://en.yibada.com/articles/118394/20160422/macbook-air-is...

Re: The average size of Web pages is now the average size of a Doom install

#287
post #183

Earlier quoted context omitted.

I think you are looking at the past through incredibly rose-tinted glasses. The web has been a mess for a long time, and we used to have to make sure our computer was set to 800x600 and we were using Internet Explorer 6 in order to even use it.

>make sure our computer was set to 800x600 Thaaaaaaaat's nonsense. I had relatively high-res CRTs (1600x1200) in the late 90s and early 2000s. My father and I were able to get by with Netscape Navigator and Firefox for quite awhile as well.

Even the first NeXT computer in 1990 was 1120×832...albeit greyscale...still...800x600 died in the mid-90s - especially for professionals.

Re: The average size of Web pages is now the average size of a Doom install

#288
post #245
post #161

Earlier quoted context omitted.

I think a plugin that enables the chrome "regular 2G" throttling (developer tools / network tab), permanently, for anyone that works in marketing or web development might help :) Edit: Joking aside, that throttling feature is a nice easy way to let a dev team, or business counterpart, see what their site is like for say, a customer with a low-end DSL connection: https://developers.google.com/web/tools/chrome-devtools…

I have to think that the devs want to make the page lighter, but their managers keep pushing more tracking and ad networks at them that they're forced to integrate.

Yeah, but I've seen projects using bootstrap, themes, extensions, and extras... in addition to jQueryUI & Mobile all loaded... as well as 2-3 versions of jQuery in different script tags.

That doesn't reflect responsible, light-minded development. Hell, load a couple of Airline website home pages... I don't think any of them are loading uncer 400kb of JS. that's for the homepage alone. Let alone the number of individual assets being requested (less of an issue once http/2 takes hold.. but still.

Re: The average size of Web pages is now the average size of a Doom install

#289
post #245

Earlier quoted context omitted.

I have to think that the devs want to make the page lighter, but their managers keep pushing more tracking and ad networks at them that they're forced to integrate.

I'm sure that's true of a certain class of developer. However, given what I've seen in the frontend & JS community in past years, I don't think there is a pervasive desire to make pages lighter. If it is, very few of them are showing that in the way they actually build things.

Especially, since many frameworks are really easy to use from source (Bootstrap comes to mind), but almost nobody does... they have the framework, the patched css, and then in the project, maybe there's scss/less etc. Instead of having a project that starts off composed with the appropriate pieces of bootstrap.

That's just bootstrap, not even the shear number of jQuery UI bits floating around, and heaven forbid you see both in a project.. and all the "bugs" that the input in one page doesn't match others. sigh

Post reply on HN