3 ms·
I'd much rather do this (which isn't all that difficult in the end?) then chasing performance issues in the web stack, which are a lot harder to chase down and
by detaro 5y ago
I'd much rather do this (which isn't all that difficult in the end?) then chasing performance issues in the web stack, which are a lot harder to chase down and fix, because the browser is a massive layer of the rendering process you can't easily tweak. (I've seen that in customer projects where I'm sure that if they had done it natively, the issues would have been easy tweaks to their engine, but instead they spent weeks on trying to understand how to get the browser to do the right thing)
- pjmlp 5y agoNot even that, there is no control over what the browser blacklists, no debuggers for WebGL (just SpectorJS kind of), and no matter what, it is just OpenGL ES 3.0.