How web bloat impacts users with slow devices:
Conversation
Notices
-
Embed this notice
Dan Luu (danluu@mastodon.social)'s status on Sunday, 17-Mar-2024 07:39:00 JST Dan Luu
-
Embed this notice
Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Monday, 18-Mar-2024 03:25:07 JST Haelwenn /элвэн/ :triskell:
@danluu Quite interesting how things compare, I guess it could be useful to have JS sizes vs. image sizes, for example Squarespace being bigger than reddit but managing to load. (after 16s though, this is seriously bad) -
Embed this notice
Andrew Kelley (andrewrk@mastodon.social)'s status on Monday, 18-Mar-2024 09:53:29 JST Andrew Kelley
@danluu I really enjoyed this post. Thank you for putting it together.
I think you might find the new zig standard library documentation web app interesting, since I made the controversial decision to have it fetch all the source code up front and then do all the content rendering locally. In theory, this is CPU intensive but in practice... even those old phones have really fast CPUs!
https://ziglang.org/documentation/master/std/
I'm curious how it fares with those old phones you have.
-
Embed this notice
Dan Luu (danluu@mastodon.social)'s status on Monday, 18-Mar-2024 09:53:29 JST Dan Luu
@andrewrk On the Tecno Spark 8C, this uses a fair amount of CPU up front (4.7s), but interaction is (relative to other sites using the same device) decently quick when you tap any target or scroll one of the pages if you scroll a page that has enough content to scroll.
I think that's really interesting. I'll add a bit about this in the post.
Haelwenn /элвэн/ :triskell: likes this.
-
Embed this notice