The Bullshit Web

Post by JdeBP » Wed, Aug 01, 2018, 11:02 AM UTC

bartread wrote: post #225

ChuckMcM wrote: post #132

Earlier quoted context omitted.

I like this rant, you should go the next step: All you need to 'fix' this is a fast loading news website that gets enough paid subscribers to earn enough margin from subscriptions that you can pay for a news staff, an office, and various overheads. That is a longish way of saying that 99.9% of the overhead in any modern web site can be traced almost entirely to the mechanisms by which that web site is attempting to e…

> That is a longish way of saying that 99.9% of the overhead in any modern web site can be traced almost entirely to the mechanisms by which that web site is attempting to extract value from you for visiting/reading. Well, that and the fact that front-end developers just can't seem to exist without pulling in hundreds of kilobytes, or even megabytes, of JS libraries. You actually don't need all that crap to serve adv…

Post by madeofpalk » Wed, Aug 01, 2018, 11:11 AM UTC

ChuckMcM wrote: post #132

cheezymoogle wrote: post #5

I've said this before, but it bears repeating: Moby Dick is 1.2mb uncompressed in plain-text. That's lower than the "average" news website by quite a bit--I just loaded the New York Times front page. It was 6.6mb. that's more than 5 copies of Moby Dick, solely for a gateway to the actual content that I want. A secondary reload was only 5mb. I then opened a random article. The article itself was about 1,400 words long…

I like this rant, you should go the next step: All you need to 'fix' this is a fast loading news website that gets enough paid subscribers to earn enough margin from subscriptions that you can pay for a news staff, an office, and various overheads. That is a longish way of saying that 99.9% of the overhead in any modern web site can be traced almost entirely to the mechanisms by which that web site is attempting to e…

Post by tim333 » Wed, Aug 01, 2018, 11:16 AM UTC

nostromo wrote: post #15

It's not just publishers. My current org uses SalesForce and it's frustratingly slow. Opening a single record takes several seconds as every single interface element is generated dynamically and then populated, seemingly one at a time. When it's finally done loading, you click on a dropdown, and then the dropdown just shows you a loading spinner, as your client asks the server what should be populated in the dropdown…

Post by moviuro » Wed, Aug 01, 2018, 12:02 PM UTC

dredmorbius wrote: post #458

moviuro wrote: post #442

I see no one mentioned the extraordinary "Reader mode" of Firefox. [0] It's literaly the one feature for which I stopped using Chrome at work. It's just so damn good. For instance, [1] becomes [2] [0] https://support.mozilla.org/en-US/kb/firefox-reader-view-clu... [1] https://radiobruxelleslibera.com/2018/06/26/intermediated-of... [2] https://lh3.googleusercontent.com/smexxUICwLXKbzEEbLlIPQ_qGc... (that's a screensho…

FYI, the Google Photos link requests a login.

Post by mrob » Wed, Aug 01, 2018, 12:08 PM UTC

cheezymoogle wrote: post #155

TeMPOraL wrote: post #149

Earlier quoted context omitted.

How much of the data downloaded is actually for typography? Also, browsers have good enough typography by default, which can be controlled with CSS.

Everyone's favorite example of that kind of "brutalist" design: http://bettermotherfuckingwebsite.com/