Hacker News Reader

Comment by outworlder | Hacker News Reader

> It put my laptop on Takeoff mode (fan's full speed!) with Firefox. This is why all this movement to rebuilding a browser in browser is ineffective.

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.

View on HN

You missed the point that it doesn't work at all, so it is obviously broken in someway in Firefox.

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 broken in Chrome too - there's no content asides from 'Reach three fibre' and the links. I would have expected at least a description to exist on the page.

I would have expected at least a description to exist on the page.

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

I ran it both in Chrome and Firefox, seems to be working. Could i bother you for error logs?

Well, it appears broken for me... But I don't have any errors in the logs.

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.)

I googled that, looks like an issue in FF: https://github.com/mrdoob/three.js/issues/9716 Basically i just channel through regular three without creating much of a dependency. If it doesn't work in react-three-fiber, then i doesn't work in threee-js. But they're so big that usually these webGL bugs are either fixed quickly by them, if it's their fault, or they're filling vendor issues.

three.js have marked it as a wontfix and referred it onto Firefox. It's sitting in Bugzilla as a 6-month+ old bug.

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.

Reply on news.ycombinator.com