How do you read this thing? All I see is "React Three Fiber".
It put my laptop on Takeoff mode (fans full speed!) with Firefox.
It put my laptop on Takeoff mode (fans full speed!) with Firefox.
Non sequitur.
Your computer is doing more processing. There's WebGL, which will engage your graphics card. If it is on your CPU, the CPU will consume more power. Depending on your laptop, you could have a discrete graphics card, which will be switched to and consume more power. There are animations, etc.
It is not only because of React. In fact, by avoiding unnecessary DOM changes, it's probably an advantage (although this would have to be measured).
Unless you are telling us that you were playing fortnite or something and your fans didn't spin up, but this thing caused them to spin up.
I run multiple VMs and do 3d work (in fact, mostly direct opengl stuff) on my laptop and it hardly ever goes to takeoff mode with just some simple rendering.
It's a work-in-progress demo of react-three-fiber. There's a good explanation of what it is on the Github page - https://github.com/drcmda/react-three-fiber
Firefox 65.0.1 (64bit), Linux (5.0.0).
There are a couple warnings about a particular extension:
> warning: extension `GL_ARB_gpu_shader5' unsupported in fragment shader
The rest just appears to be successful parsing messages.
(But it worked really well in Konqueror & Chromium, so that's something.)
Safari and Chrome both had to work around the same thing, so it seems like there's some contention around who is to blame here.
Either way, three.js is (partially) broken for Firefox users.
None of the demos work on Firefox.