The Browser's Main Thread Is Expensive

piker•41 minutes ago

Great piece, OP. We work in WASM and are considering web workers to help with rendering documents off the main thread in that context. I was surprised to read that ArrayBuffer is moved by reference only! Might be an option. Thanks for putting this together.

xnorswap•31 minutes ago

Excellent article, I went into it thinking the headline is obvious, but the examples are well crafted and it isn't just the obvious stuff.

nairboon•about 1 hour ago

In the first example: doesn't pushing the button while typing cause the textfield lose focus? What's the point of the typing in the example?

lintfordpickle•43 minutes ago

I think the point is, if you click the '2.0s' button, you cannot re-focus on the input field for those 2 seconds.

Tepix•about 1 hour ago

Nice examples, a bit repetetive perhaps.

One thing that I found quite interesting to see is how the behaviour of the "4.000 particles" demo changes between the 5ms rendering and the "everything now" rendering.

adzm•37 minutes ago

I wish await in JavaScript could conditionally yield. Instead I end up having to use arounds like if (shouldYield()) await do yield();

baxuz•33 minutes ago

There's an RFC or two to spawn threads so I'm looking forward to that. The current way of workers + messages is tedious as hell.

Ayesh•about 1 hour ago

Such an excellently written articles with really nice interactive visualizations!

ahartmetz•about 1 hour ago

Yeah, but if your website with, you know, text and stuff, doesn't do any stupid and unnecessary crap, it doesn't matter where the nonexistent unnecessary yet expensive code doesn't run.

another-dave•about 1 hour ago

and if you have no website at all, it takes zero seconds to load.

But for people who are developing websites that are more than just text, this is an excellently written article and great advice.

It's funny, for mobile app dev it feels like the community are a lot of focused on staying off the main thread, this is the first time I've come across one for webdev.

adzm•44 minutes ago

Well yeah but if you do actually need things like images, animations, high frequency updates, etc, this is actually a pretty good overview of how to approach it. Also learned that react uses posting to a MessageChannel to yield!

account42•25 minutes ago

GP is right that just like with garbage where "reduce, reuse, recycle" the first question for optimizing something should be if you need to do the calculation at all.

adzm•19 minutes ago

This is true as well, yeah, but it came off as dismissive of everything too. Personally I prefer information dense interfaces with minimal chrome, but there really is a certain joy when you get to use a well designed and optimized fancy reactive, immersive interface

kodoman•21 minutes ago

Amazing how you are being so down voted, most webpages do utter crap that no one would want the webpages to be doing other then advertisers. Really most things should be text and if we lived in a more cooperative world everything would be easy to parse and manipulate text with some video and images and perhaps various well defined interface types for different services that can be implemented in various ways as to the users liking.

Tepix•about 1 hour ago

Sure, but there are sites like HN and there are sites like https://earth.nullschool.net/

What's your point? Are you saying all animations and rendering are unnecessary?

ahartmetz•31 minutes ago

My point is that many websites are using way too much technology for what they need to do, with correspondingly long load times and choppy runtime begavior.

dspillett•11 minutes ago

Correct. But if the page is, at least in part, an art piece rather than an information dump, or needs to do interactive rendering for its purpose (an editor like the markdown example, live updating status displays, games and other interactive toys, etc), then the tech is necessary and this article is useful.

The Browser's Main Thread Is Expensive

⚡ Community Insights

Discussion (18 Comments)Read Original on HackerNews