Live data from Hacker News

The browser's main thread is expensive

kciter.so

31–40 of 167 posts

Re: The browser's main thread is expensive

#31
post #10

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.

[deleted]

Re: The browser's main thread is expensive

#32
post #10

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.

haven't done this for documents, but for canvas rendering transferControlToOffscreen() worked better than moving ArrayBuffers. It hands the canvas to a worker that draws directly, no pixles over postMessage at all.

Re: The browser's main thread is expensive

#33
Top article, kudos! applied some of these techniques previously, and they do matter a lot. thing is, when you learn/teach JS there is usually limited time left to talk these topics, and they are essential more than it seems.

the whole point of cooperative multitasking is to yield now and then (back to the runner), so that it can process the drawing. Besides, at 60fps there's so much that can be computed once every N frames, and the eye does not see it, the animation flows.

It becomes even more interesting when webgpu is involved, but the CSS animator is indeed very fast.

note: some recent work of mine (newskool digital flyer sites) -> bsf.hmsu.org // nouveauxhivers.dub4powder.xyz

Re: The browser's main thread is expensive

#35

So this is AI slop written? Why would anyone believe I'd want to read AI spam? Also, the issue I see is who controls browsers as much more profound. We need to find a solution here, as the browser is too important to allow private companies to keep mankind hostage. Edit: Wow, and the praise-accounts. Is that new on hackernews?

What signs of slop are people seeing here? Or is it just a knee-jerk reaction to encountering lots of text?

I’ve worked in the field for a long time and see a carefully written, correct, calm article. No obvious AÍ tells in wording or sentence construction. It is a bit long - might have been inspired by ciechanow.ski

Re: The browser's main thread is expensive

#36

So this is AI slop written? Why would anyone believe I'd want to read AI spam? Also, the issue I see is who controls browsers as much more profound. We need to find a solution here, as the browser is too important to allow private companies to keep mankind hostage. Edit: Wow, and the praise-accounts. Is that new on hackernews?

What signs of slop are people seeing here? Or is it just a knee-jerk reaction to encountering lots of text? I’ve worked in the field for a long time and see a carefully written, correct, calm article. No obvious AÍ tells in wording or sentence construction. It is a bit long - might have been inspired by ciechanow.ski

"and there’s a reason for that" "The code isn’t slow. It just happens to be the code that’s holding the main thread." "dealing with the main thread becomes the important part" "What to remember for now is that holding the main thread for a long time is the same thing as freezing the screen." "One thing not to misread here is"

I realize the author may not write native English, but this is not translation slop, it's AI writing slop.

Post reply on HN