Re:Treble: A modular base for Android
by CyberDildonics on Saturday May 13, 2017 @09:29AM
(#14330852)
It absolutely does. If webasm works out this is how I see things going. Android is already running things through a JIT.
I don't think users want dozens of apps installed on their phone, each with the possibility to be using up bandwidth, hogging resources, stalling programs and draining battery life, not to mention abusing permissions. If most apps can be done with webasm (and I don't see why the majority of apps can't be) then the only things that need to run in a more native context would be apps that use special features.
It also does AOT compilation with PGO gathered from the JIT.
Unless the browsers offer APIs at the same feature level as native OS APIs, web applications will always be a second class experience.
Re:Treble: A modular base for Android
by CyberDildonics on Monday May 15, 2017 @08:51AM
(#14341135)
Only for apps that need those native features.
Re:Treble: A modular base for Android
by chiefalchemist on Tuesday May 16, 2017 @07:16AM
(#14348726)
For example? As in, what doesn't Phone Gap offer access to?
But in any case, to your point, native apps should be limited to special cases (that can't be done via the browser). That's not the case ATM.
Which means any app that respects its users by providing a suitable UI/UX using the best features of the OS running on the device they paid for.
Re:Treble: A modular base for Android
by CyberDildonics on Tuesday May 16, 2017 @09:09AM
(#14349231)
What does that even mean? Lots of apps don't need anything that isn't already exposed in newer web apis.
It absolutely does. I'm helping out on a bespoke app that needs to run on some discount Chinese tablets that are stuck on Android 4.something, and it's easier to target Chrome (which is still being updated) than the OS itself.
To some extent doesn't this make a case for (say) HTML# and browser based apps? That is the browser is a known sandbox of sorts. It's interface with the device (e.g., Phone app) is a known, and fixed. It has no care about what's on the other side of that wall. And the device OS more or less exists to run and support the browser.
But when the applications interface directly with the device, and there are countless device and OS, etc. combos there will always be a mess. Too many variables. Too many chefs in the kitchen if you will.
I realize I probably oversimplified. (Sorry.) I'm also outside my knowledge sweet spot, but am curious enough to want to learn. Please don't hurt me. Thank you.