Read on Twitter
Writing modern UIs has much more in common with writing games than with any other software.
Native vs Web, a short thread
Native vs Web, a short thread
Native app development toolkits are game engines. They supply higher-level wrappers around low-level primitives, and if you use them correctly, you get decent performance.
Correctly ≠ Naïvely
Correctly ≠ Naïvely
When your application tries to do something unique, you must leave the comfortable abstraction and deal with the low-level shit yourself.
That is game development in a nutshell. You invest a lot of time and labor into the parts of your game/app that are unique.
That is game development in a nutshell. You invest a lot of time and labor into the parts of your game/app that are unique.
The web has the lower-level primitives but very few people take advantage of them. People think that it's a failure if you have to spend that time and energy.
I don't know why the expectations are different on the web.
I don't know why the expectations are different on the web.
60fps is achievable on the web. You must think like a game developer writing close to the metal:
Eliminate unnecessary work, everywhere
Offload operations to the GPU where possible
Expect to manually draw things pixel-by-pixel instead of using the DOM
Eliminate unnecessary work, everywhere Offload operations to the GPU where possible Expect to manually draw things pixel-by-pixel instead of using the DOM
