3 ms·
It will drain the battery a lot faster on a laptop or phone. And use more power and CPU on a desktop machine. Game engines and their rendering models are usual
by cmrdporcupine 2y ago
It will drain the battery a lot faster on a laptop or phone. And use more power and CPU on a desktop machine.
Game engines and their rendering models are usually doing work every frame by nature of their design. A retained mode, event based GUI doesn't need to.
That and you can basically say goodbye to hooks for accessibility, common/standard shortcuts, etc.
- akkartik 2y agoThe power point is not true. Game engines are forced to be efficient and can use little power if the number of game objects they're managing is limited. The power usage I see is: web browser running a document << game engine running a simple UI << web browser running a simple UI on wasm << game engine running a serious AAA game. The accessibility point is very valid.
- kragen 2y agoA UI that's displaying a document ought to be as efficient as a web browser "running" a document, which I think you're saying here uses much less power ("<<") than a game engine running a simple UI. So it sounds like you're saying that a game engine running a simple UI will drain the battery a lot faster on a laptop or phone than running the same UI in a retained-mode fashion. You may recall that the fact that LÖVE does in fact drain the battery on my laptop a lot faster running simple UIs has been a strong disincentive for me to use simple UIs written in LÖVE!
- Rohansi 2y agoNot necessarily. By default they will continuously render frames but some are capable of skipping frames when nothing is changing. However this is a manual optimization to perform whereas using a proper UI framework would handle it automatically.