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

How web bloat impacts users with slow devices

danluu.com

Post reply on HN
Print view View original

191–200 of 613 posts

Re: How web bloat impacts users with slow devices

#191

Post by a_bored_husky »

Cacti wrote: post #180
zozbot234 wrote: post #161

Earlier quoted context omitted.

> That's good enough to use Discourse at all, but the experience will probably be on the unpleasantly slow side. ... an alternate "lite/basic" mode Why does this need to be the "alternate" choice though? What does current Discourse provide that e.g. PhpBB or the DLang forum do not? (Other than mobile friendly design, which in a sane world shouldn't involve more than a few tweaks to a "responsive" CSS stylesheet).

Voice, video, realtime interaction, a devoted user base, an incredible amount of money…

Discourse, not Discord.

Re: How web bloat impacts users with slow devices

#192

Post by spintin »

throw_m239339 wrote: post #25

Every company stopped caring, especially the companies who were at the forefront of standards and good web design practices, like Google and Apple. Google recently retired their HTML Gmail version, mind you, it still worked on a 2008 256MO RAM Android phone with an old Firefox version and it was simply fast... of course the new JS bloated version doesn't, it just kills the browser. That's an extreme example, yet low…

Yes, on Thursday Google ended their only viable "product".

RIP Google.

The new Reddit is unusable, and the old is well too old.

Twitch is borderline usable, with chat and video stream problems...

The list is long...

All changes are bad when you have the final formula because they are job security.

Eventually the monkeys on this ball of dirt will realize that jobs and money don't exist, but then it will be to late... oh that is now!

RIP Humans.

Re: How web bloat impacts users with slow devices

#193

Post by logtempo »

myself248 wrote: post #114

Where "users with slow devices" equals "anyone trying to keep hardware running more than a few years", it seems. It's enforced obsolescence. I've said for a long time, devs should be forced to take a survey of their users' hardware, and then themselves use the slowest common system, say, the 5th-percentile, one day a week. If they don't care about efficiency now, maybe they will when it's sufficiently painful.

thing is, boss is not a dev. He is a business man.

Re: How web bloat impacts users with slow devices

#194

Post by zelphirkalt »

Cacti wrote: post #180
zozbot234 wrote: post #161

Earlier quoted context omitted.

> That's good enough to use Discourse at all, but the experience will probably be on the unpleasantly slow side. ... an alternate "lite/basic" mode Why does this need to be the "alternate" choice though? What does current Discourse provide that e.g. PhpBB or the DLang forum do not? (Other than mobile friendly design, which in a sane world shouldn't involve more than a few tweaks to a "responsive" CSS stylesheet).

Voice, video, realtime interaction, a devoted user base, an incredible amount of money…

What do you mean by voice and video? Why would I want to have voice in a forum? I think that would be akin to receiving voice messages in messengers. Or do you mean, that for these kinds of things a widget can be displayed? That certainly is possible in old style forums. It is just HTML, an embed code away.

Re: How web bloat impacts users with slow devices

#195

Post by dsr_ »

mastazi wrote: post #178

> While reviews note that you can run PUBG and other 3D games with decent performance on a Tecno Spark 8C, this doesn't mean that the device is fast enough to read posts on modern text-centric social media platforms or modern text-centric web forums. While 40fps is achievable in PUBG, we can easily see less than 0.4fps when scrolling on these sites. Remember this the next time marketing asks the frontend team to impl…

To be fair, it is usually difficult to tell the difference between 243 tracking scripts and 244.

Re: How web bloat impacts users with slow devices

#196

Post by emodendroket »

mastazi wrote: post #178

> While reviews note that you can run PUBG and other 3D games with decent performance on a Tecno Spark 8C, this doesn't mean that the device is fast enough to read posts on modern text-centric social media platforms or modern text-centric web forums. While 40fps is achievable in PUBG, we can easily see less than 0.4fps when scrolling on these sites. Remember this the next time marketing asks the frontend team to impl…

> Remember this the next time marketing asks the frontend team to implement that new tracking script and everyone assumes that users won't even be able to tell the difference.

I mean, maybe they can but the business doesn't care. If you polled "users" of cable television I doubt anyone would say they prefer the experience of commercials.

Re: How web bloat impacts users with slow devices

#197

Post by MiddleEndian »

ryukoposting wrote: post #5

I only recently moved from a 6-year old LG flagship phone to a shiny new Galaxy, and the performance difference is staggering. It shouldn't be - that was a very high-end phone at release, it's not that old, and it still works like new. I know it's not just my phone, because the Galaxy S9s I use to test code have the same struggles. I would like to have seen Amazon in the tests. IME Amazon's website is among the absol…

I have a Palm Phone. I generally consider web browsing to be almost impossible no it at this point lol

Re: How web bloat impacts users with slow devices

#198

Post by wolpoli »

squarefoot wrote: post #188
pixl97 wrote: post #116

Earlier quoted context omitted.

> That means no ublock origin Talk about a catch-22 situation. The modern web is useless without adblocking. Especially when you get forever scrolling pages with random ads stuffed in there.

As a web developing illiterate, I wonder how hard would be writing a browser extension that loads a page, does infinite scroll in memory and in background, then while it is still loading the infinite stuff, splits the content in pages and shows them instead, so that the user can go back and forth to page numbers. This wouldn't reduce the network and system load, however navigating the results would be much more frien…

It'll give a nicer experience and will eliminate situation where an element changes location just as you try to tap on it.

The extension just needs to handle GDPR notice and Email subscription overlays.

Re: How web bloat impacts users with slow devices

#199

Post by [deleted] »

zozbot234 wrote: post #161
bluquark wrote: post #66

Dan's point about being aware of the different levels of inequality in the world is something I strongly agree with, but that should also include the middle-income countries, especially in Latin America and Southeast Asia. For example, a user with a data plan with a monthly limit in the single-digit GBs, and a RAM/CPU profile resembling a decade-old US flagship. That's good enough to use Discourse at all, but the exp…

> That's good enough to use Discourse at all, but the experience will probably be on the unpleasantly slow side. ... an alternate "lite/basic" mode Why does this need to be the "alternate" choice though? What does current Discourse provide that e.g. PhpBB or the DLang forum do not? (Other than mobile friendly design, which in a sane world shouldn't involve more than a few tweaks to a "responsive" CSS stylesheet).

[deleted]

Re: How web bloat impacts users with slow devices

#200

Post by duck2 »

spintin wrote: post #189
mastazi wrote: post #178

> While reviews note that you can run PUBG and other 3D games with decent performance on a Tecno Spark 8C, this doesn't mean that the device is fast enough to read posts on modern text-centric social media platforms or modern text-centric web forums. While 40fps is achievable in PUBG, we can easily see less than 0.4fps when scrolling on these sites. Remember this the next time marketing asks the frontend team to impl…

PUBG is now a very special beast: It's CPU bound = we are unlikely to ever see a "AAA" game with anything beyond it's complexity for eternity. You can run it on a 1030 GPU at 60 FPS.

It's not like websites are GPU bound
Post reply on HN