3 ms·
I would argue that it is obviously worth it for the simplicity of being explicit what is the next state. This kind of performance optimization, especially outs
by kochthesecond 9y ago
I would argue that it is obviously worth it for the simplicity of being explicit what is the next state.
This kind of performance optimization, especially outside of game engines seem unnecessary.
- cube2222 9y agoThis is Rust. Not exactly a language that makes compromises on performance for the sake of simplicity.
- vvanders 9y agoEach cycle you waste on mobile is milliwatts you're burning from the battery. Even if the user doesn't perceive it their battery will appreciate it.
- kochthesecond 9y agoYou save a single allocation for every state change in your app? Never mind the actual render cycle? And lose a simple reference check to decide if you can short-circuit a part of your app?