Hacker News Reader

Comment by ezekg | Hacker News Reader

It does turn off when it detects a low-end or integrated GPU. But something may not be working correctly, or is getting miscategorized.

That's why the debug information would help.

View on HN

When you emailed me about this a few weeks ago I played around a bit with the shader, and just creating fewer blobs made the problem go away (reducing "for (int i = 0; i < 15; i += 1) {" to 5 in the "void main"), but I didn't really have the time to investigate in-depth or see what kind of visual effects that would give (dealing with this minified JS isn't exactly fun and I never worked with OpenGL shaders either), but just FYI.

Good to hear it's not just me though (and the effects also aren't disabled for me either).

Or, again, turn it off and avoid the whole class of issues, wasted time and asking random HN folk for debug logs.

Don’t listen to random comments on hacker news. It looks cool OP. Don’t throw out the whole thing for a few bugs

Yeah, as long as we're focused on the really important things. Like animations that nobody actually needs or wants (apart from the person putting it there). That is, of course, until it ruins the user experience by bogging down the browser. And then, sure, let's debug that and make sure it runs on everyone's browser/os/cpu/gpu combo. That's a brilliant use of time.

Until someone turns up with a new combo where it doesn't work. Because judging by the comments, this seems to be a janky piece of code that isn't well understood.

"Turn it off" (or rather, "rip it out, and throw it away" is good advice. If there is even a slight chance this might come back to haunt you and screw the user experience, it isn't worth it. If your animation is more important than avoiding a horrible user experience, well, that's kind of useful for your customers I suppose.

How do you imagine user conversations take place, if not from "random HN folk"?

Do you want an appointment? A lab?

Reply on news.ycombinator.com