5 ms·
There's a couple of points going around in my head which I find interesting / relevant when it comes to emscripten/asm.js, the web and mobile platforms: - asm.
by flohofwoe 12y ago
There's a couple of points going around in my head which I find interesting / relevant when it comes to emscripten/asm.js, the web and mobile platforms:
- asm.js code runs faster then Java code running through the Dalvik VM on Android (https://blog.mozilla.org/javascript/2013/08/01/staring-at-the-sun-dalvik-vs-spidermonkey/ https://blog.mozilla.org/javascript/2013/08/01/staring-at-th...)
- porting and cross-compiling code to JS with emscripten is (arguably) easier then setting up and working with the Android NDK
- the new Javascript LLVM backend in iOS8 Safari runs asm.js code very well, and Safari on iOS8 adds WebGL support
- the web is a the only open software distribution platform without gate keepers (seriously, this is starting to get ridiculous: https://developer.apple.com/app-store/review/guidelines/ https://developer.apple.com/app-store/review/guidelines/)
- web apps don't need all the code-signing and certification hoopla that native mobile apps need to go through
- app shops are becoming saturated and have the same or worse visibility problems as the web even though they are 'curated'
- you don't pay the 30% platform tax on the web (or rather: you're free to choose your store front-end)
- in the end, most successful mobile games need so little CPU and GPU performance that it really doesn't make a difference whether they run native or in BASIC, WebGL or Metal
I think that the advantages that a single centralized app-shop offered in the past over the web have already or will erode very fast once they have to manage a very high number of apps, basically modern AOLs but with shitty search engines. The open web is the only way out, even if it just means that multiple, decentralized app shops will be built on which compete with each other.
[edit: formatting]
- micampe 12y agoYou listed only the positives of one platform, you forgot the other side of the equation: its negatives and the other platform's positives.
- flohofwoe 12y agoTrue, apologies for that. It is because I've been working with iOS and Android longer and take their advantages for granted (although I find it hard to find much nice things to say about C/C++ development on Android). emscripten and the web is still the "new platform" for me.
- octaveguin 12y agoI love the idea that we can make web apps just as successful as native apps, but the reality seems to be the opposite. Mobile web usage went from 20% to 14% according to flurry from 2013 to 2014. That trend could be reversed with a new movement towards the web, but it seems like it would take quite a trend reversal. We're stuck with apple- and google- based rent seeking platforms. http://www.flurry.com/bid/109749/Apps-Solidify-Leadership-Six-Years-into-the-Mobile-Revolution#.VA7d-oC1a8U http://www.flurry.com/bid/109749/Apps-Solidify-Leadership-Si...
- espadrine 12y agoWe need installable, offline web apps. They are working on it, but it is late. https://github.com/w3c/manifest https://github.com/w3c/manifest (I should note that technically, AppCache + bookmarking provides installable web apps, but nobody seems to want to program with AppCache, and bookmarking doesn't really feel like installing an app, which it should.)
- giancarlostoro 12y agoThey exist with a different approach from what you're thinking: CherryMusic - https://github.com/devsnd/cherrymusic https://github.com/devsnd/cherrymusic SABnzbd - http://sabnzbd.org/ http://sabnzbd.org/ Desktop applications with a Web Based UI I think is the way to go. I love Desktop applications, but being able to just open a browser and use an app from my phone or tablet, regardless of whether they're iOS or Android, or whatever is better than developing a full blown native application that doesn't work "everywhere". There's more applications like that, but I leave that fun to others.
- M2Ys4U 12y agoAppCache sucks. It's completely broken. At least we have the Service Workers spec[0] coming soon, though, which should solve the problem. [0] https://github.com/slightlyoff/ServiceWorker/ https://github.com/slightlyoff/ServiceWorker/
- constexpr 12y ago
- phaer 12y ago"- web apps don't need all the code-signing and certification hoopla that native mobile apps need to go through" You mean that's a good thing? I'd prefer a clear signing process for software to a web service running its backend on some random server where it's impossible for me to establish trust.
- icebraining 12y agoYou can have offline, signed web apps as well. It's just that with web apps, it's optional. For example, see how Firefox OS handles it: https://developer.mozilla.org/en-US/Marketplace/Options/Packaged_apps https://developer.mozilla.org/en-US/Marketplace/Options/Pack...
- fulafel 12y agoGoogle and Apple stores are full of clone apps, privacy violations, and worse. They still have ad networks and other backend services that the apps communicate with. Those conspire to sell your personal info to the highest bidder (or exploit you in some other creative manner) and have no incentive to do nice by you.
- duaneb 12y agoCode signing isn't about cloned apps or privacy violations, it's a mechanism to communicate DISTRUST by revoking it. How does removing that help the consumer?
- phaer 12y agoCorrect, my argument was more about the concepts than the concrete implementations. I don't use Apples AppStore and I don't like Googles Playstore, but things like fdroid are quite nice.
- anon1385 12y ago>the web is a the only open software distribution platform without gate keepers The browser vendors are gate keepers. They decide what your code can and can't do inside the very restrictive javascript sandbox.
- azakai 12y agoIn some sense, sure. But at least 1. They are a group of vendors instead of a single vendor that can do whatever it wants, and 2. They don't have arbitrary rules that they apply inconsistently, which we see on app stores sometimes