Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

mobiforge.com

Post reply on HN
Print view View original

261–270 of 467 posts

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

#261

Post by JustSomeNobody »

delan wrote: post #208
JustSomeNobody wrote: post #111

Earlier quoted context omitted.

We absolutely, most certainly, should NOT ship libraries with browsers. This is a horrible idea. Browser vendors would then have too much influence on development libraries.

“We absolutely, most certainly, should NOT ship libraries with operating systems.”

All the major browsers ship with JavaScript.

If JS, absolutely needed JQuery in order to, say, select an element the way C needs a library to output to the console, then sure, you may have an argument here.

But, no.

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

#262

Post by JustSomeNobody »

ArkyBeagle wrote: post #232
delan wrote: post #208

Earlier quoted context omitted.

“We absolutely, most certainly, should NOT ship libraries with operating systems.”

There used to be a distinction between browsers and operating systems.

Pretty sure there still is.

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

#263

Post by JustSomeNobody »

LeoNatan25 wrote: post #207
mod wrote: post #167

Earlier quoted context omitted.

It could be a 'use the default or link your own' situation, which then wouldn't influence a whole lot. But I agree, overall.

In this case, very very little would change. People would still link their own, as they do now.

Or worse, people would use the buggy, out of date default.

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

#264

Post by K0nserv »

recursive wrote: post #257
Retr0spectrum wrote: post #254

Earlier quoted context omitted.

I'm a fan of white-on-black too, but whatever setting/addon you are using to acheive that effect seems to be very broken. It's unfair to blame BMFW for a problem created by, and unique to, your specific configuration.

The setting isn't broken. It's not an add-on. It's BMFW's fault, and it's fair to blame it for this. BMFW sets a foreground color, and does not set a background color. Here are the settings in stock Firefox. http://imgur.com/h4SmKYs

The author even addresses the fact that they didn't set the background on the site.

"I would've even made this site's background a nice #EEEEEE if I wasn't so focused on keeping declarations to a lean 7 fucking lines."

Also the whole site is satire which you seemed to have missed

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

#265

Post by dexterdog »

AnkhMorporkian wrote: post #116
newjersey wrote: post #104

Earlier quoted context omitted.

What if the checksum was the same and you accepted the cache hit if the checksum agrees and get your own copy if it doesn't? Maybe the application should get to declare a canonical URL for the js file instead of the browser? So something like https://ajax.googleapis.com/ajax/libs/jquery/1.12.2/jquery.m... sha-256="31be012d5df7152ae6495decff603040b3cfb949f1d5cf0bf5498e9fc117d546"> Would this cause more problems than i…

> I'm concerned about people like me who use noscript selectively. How easy is it to create a malicious file that matches the checksum of a known file? SHA-256? Very, very, very, very hard. I don't believe there are any known attacks for collisions for SHA-256.

And if you worry about that you can always use 384. Plus a side benefit is that 384 is faster on a 64-bit processor.

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

#267

Post by davidivadavid »

Joeri wrote: post #245
tyingq wrote: 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.

Doesn't Segment.io address such issues?

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

#268

Post by jakobdabo »

Yesterday I discovered that Twitter's HTTP headers alone are ~3500 bytes long (25 tweets!) with several long cookies, custom headers and the Content Security Policy[1] containing ~90 records. Is this considered normal nowadays?

[1] https://en.wikipedia.org/wiki/Content_Security_Policy

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

#269

Post by kedean »

logotype wrote: post #253
tyingq wrote: 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…

No need for a plugin if you are running Linux or OSX: # Bandwidth trottling, enabling 150kB/s on port 80 sudo ipfw pipe 1 config bw 15KByte/s sudo ipfw add 1 pipe 1 src-port 80 # Bandwidth trottling, disable sudo ipfw delete 1 More useful stuff here as well, please star the repo :) https://github.com/logotype/useful-unix-stuff/blob/master/us...

It's not a plugin, it's built into chrome. His joke was about a plugin that enables it permanently for certain people.

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

#270

Post by tyingq »

Joeri wrote: post #245
tyingq wrote: 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.

That's true in some cases, but there are lots of big company sites with no ad networks that are crazy bloated and slow. Some have trackers, but would be bloated (2,3,4MB+ over the wire) without them as well.
Post reply on HN