Hacker News Reader

Comment by Lorin | Hacker News Reader

So many DOM elements, if you inspect a wall it's made from thin slices. Wonder if they could be merged to form complete 'walls' and then use gradient effect... heck, SVG may be more effective.

View on HN

That's right, which is actually kind of the point. It's amazing that 320 divs can be shuffled around the screen at 60 fps. Browsers are amazing!

It's amazing that 320 divs can be shuffled around the screen at 60 fps. Browsers are amazing!

Don't tell that to a game dev

Ha, yeah. I gave a talk on this project once and pointed out that "If it's possible to do on 1980's hardware, it's possible to do in React".

Also, I'm pretty sure there are many websites out there pushing around way more divs than this is.

Guilty.

It's because CSS transforms that don't affect layout happen on the GPU, so they may as well be polygons. In fact ThreeJS, the most prominent JS library for 3D rendering in WebGL, can work in DOM rendering mode instead of WebGL :)

I've been playing around with some very extreme forms of server side rendering, and have come to discover that all modern browsers can actually decode and display 1080p+ jpeg images streamed over websocket fast enough to be indistinguishable from a x264 video playing at the same frame rate (60fps in my testing). I have tried on ARM/mobile and it's the same success story there. Latency almost feels lower on my S10 than my Threadripper 2950X.

There's lots of things a browser can do that would surprise a lot of developers.

If the goal is to have a raycaster you ought to have thin slices.

Table with 320 columns? TD elements with rowheight attributes?

Reply on news.ycombinator.com