News for hackers. Stuff that matters.

A comment on Android, evolvability and Comcast. Parent comment

Re:Android, evolvability and Comcast by reilly3000 on Sunday April 23, 2017 @02:57PM (#14179756)
Because Facebook has thrown tens of millions of dollars towards getting a unified cross platform method of having 60fps rich mobile apps. Because managing an app of more than trivial complexity on iOS and Android is massively expensive. Because this approach offers the most leverage with the least trade offs of performance, development overhead, and future viability.

And because live coding mobile apps with a REPL is epic.

[ Parent | on HN ]
Re:Android, evolvability and Comcast by JustSomeNobody on Sunday April 23, 2017 @03:56PM (#14180122)
These are all developer centric points. What about users? Android already needs huge batteries, make everything run JavaScript and they'll need to be even larger. And forget computationally heavy apps? The hardware android runs on doesn't exactly have the best JavaScript performance.
[ Parent | on HN ]
Re:Android, evolvability and Comcast by jbob2000 on Sunday April 23, 2017 @09:03PM (#14181300)
I'm not sure you understand what react-native is... The app your users use isn't running javascript, it's not Facebook Cordova. You use javascript to compose the app, there's no javascript in the app you deliver to the users.
[ Parent | on HN ]
Re:Android, evolvability and Comcast by anonred on Monday April 24, 2017 @12:33AM (#14182008)
Pardon my incredulity, but if you use React, how can you not know that it uses a JS runtime? While it's not as bad as Cordova, you're hardly doing your users any favors in terms of performance by using React.
[ Parent | on HN ]
Re:Android, evolvability and Comcast by esrauch on Sunday April 23, 2017 @09:46PM (#14181430)
What? Surely the JS you write is embedded in the release build.
[ Parent | on HN ]