3 ms·
You're optimizing for the wrong resource. Computers serve humans, not the other way around. That means that unless you're optimizing for something that benefit
by wpietri 13y ago
You're optimizing for the wrong resource.
Computers serve humans, not the other way around. That means that unless you're optimizing for something that benefits people, you're probably making things worse.
So yeah, if a program is just the same but is twice as slow in a way that harms user experience, then sure, that's bad. But if a program uses twice the CPU but is easier to develop and deploy, that's a win.
For example, if somebody uses the technology to make MAME and its library available in every browser in the world, then that's great, because somebody just enabled a hell of a lot of fun.
Sure, they could try to get everybody in the world to download and install a native copy and save a bunch of CPU time that wasn't going to get used anyhow. But that'd be a big waste of human life, a much more precious resource than CPU time.
- camus 13y agotwice the cpu kills the battery on mobile/tablet => it is harming user experience. Instead of trying to be native in a browser just be native on the plateform you bring the product. The web is not good for everything.
- jasonlotito 13y agoNeither is native. And frankly, if your app is actually worth something, you should have a web version. Not everyone can afford a shiny new iPhone. And that does a thing far worse than harm the UX. It prevents those that would benefit most from using the app. You make it seem like the battery life is the only thing that matters.
- wpietri 13y agoDepends on how much CPU you're using. Any app that is using a lot of CPU on a phone will kill the battery regardless. So I agree that if you're doing something where using 2x CPU will make a significant difference and you've already optimized things heavily, then sure, go native. But I'm sure that most apps on my phone are already using 2x the CPU they could be, and I just don't care.