5 ms·
Without off screen canvas and threading your UI and logic are all being done in a single thread, causing significant lag problems that every other kind of appli
by devwastaken 5y ago
Without off screen canvas and threading your UI and logic are all being done in a single thread, causing significant lag problems that every other kind of application has resolved since the 90's. Threading is am essential part of any user facing application, and browsers outside of chrome have continually squandered the ability to put out good quality UI that does intensive background work. Something as simple as a video player in wasm requires at least 1 other thread.
- Steltek 5y agoThere's still a major disconnect in this blog post. The problem statement was making all web-enabled devices performant with Canvas, not just desktops and mobiles running Chrome. If Off Screen Canvas is only available for a recent version of one browser engine, it's not going to solve that problem is it?
- jbluepolarbear 5y agoThe core map code is slow, why doesn’t the map code optimize its runtime by using threads? Then the main thread canvas just renders the current state? That’s how you solve the problem, not by creating an entire new canvas to solve the crappy map code. You’re right, people have solved these problems with threads, but on a much better way. Google needs to stop reinventing the wheel and fix their problems.