This is a perfect example of why the problem isn’t the stack, native vs web, or programming languages. I’ve been saying this for ages when people bash JS for being slow, or the web for being bloated. Yes, you pay a bit for the sandboxing, GC, rendering, built in accessibility. But that’s a rounding error when businesses, especially large ones, go on a PM-centric feature frenzy. You get out exactly what you put in. Pe…
Depends on how you frame the problem.
If you declare the problem is that although batteries became way more efficient you don't get out more hours because they are wasted, then the story is a different one.
Same when you don't have an abundance in RAM but are forced to use certain programs and applications. I have 64GB Ram these days, colleagues at clients of mine only have 16GB and they face certain challenges I don't, because of the tools forced upon them by their superiors.
These problems can be real, they can be "artificial" (there is a philosophical note to this somewhere ;)), but in the end, there is undeniable truth that launching a whole browser engine for each and every app can be and indeed is wasteful compared to alternatives.
Of course if you don't see this as a problem "ex falso quodlibet" takes precedence and it all becomes futile to discuss :)