Hacker News new | past | comments | ask | show | jobs | submit login

At some point, these well crafted battery sipping native C apps are going to be able to live in your browser with WebAssembly and WebGL.



>battery sipping native C apps

Battery sipping native C apps? Mobile browser-based SPAs are worse battery sipping offenders than native apps.

At least the native C apps don't run 2-3 extra levels of indirection AND the most inefficient GUI stack to top.


I think they were using "sipping" as a compliment, as opposed to gulping, draining, etc.


Yes, that's what I was implying. Industry has been repeating the mantra of developer time being worth more than machine time for so long. Indeed, it's true, but far too many people forget that it's a trade off, and that machine time is still valuable. You can't just cut developer time at any expense. That's how we end up with phones that last 4 hours between charges and a vicious cycle of throwing hardware in the trash because lazy developers made it obsolete.


The point of WebAssembly and WebGL is to remove a few layers of indirection and that inefficient GUI stack.


Yet in real life use, WebGL apps suffer from spending too much time on the JS layer (for physics, instructions, etc), so they get a lot of overhead over pure OpenGL.

WebAssembly might indeed solve this...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: