5 ms·
The solution is called React Native. - Single file app: Check - Super fast rebuild: Check - Dynamic language (high reusability and one-liners): Check (Use Cl
by vikeri 9y ago
The solution is called React Native.
- Single file app: Check
- Super fast rebuild: Check
- Dynamic language (high reusability and one-liners): Check (Use ClojureScript to take this even further)
- krzyk 9y agoBut there is a single problem with React Native: Javascript (and all languages that come from it). It's frequently one of the most hated ones as it is loved. Dynamic language is not necessary the best thing invented, if it were there wouldn't be any other kind of languages.
- paulddraper 9y agoDoesn't it follow that static language is not necessarily the best thing invented, if it were there wouldn't be any other kind of languages?
- krzyk 9y agoYes, but parent response suggested that dynamic langs are the answer to android development problems. Adding more to the discussion: Android env is like a framework (as opposed to library), it is always harder to work in frameworks than using libraries - e.g. lots of stuff you will have trouble mocking out in unit tests.
- tumblen 9y agoLots of great experiences with Typescript being reported and I am loving Flowtype lately so the era of only dynamic JS is fading out. A lot of the JS hate goes out the window with ES6 and type systems.
- vikeri 9y agoI was just addressing the issues outlined in the post. I would hardly define ClojureScript as a language that came from JavaScript. Naturally there are cases when a typed language is better than a dynamic one.
- JustSomeNobody 9y agoThere is something seriously wrong with our industry. How can this even be suggested as a solution?
- moomin 9y agoI'm guessing the answer to this is: because the problem is ridiculously bad.
- reilly3000 9y agoBecause 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.
- JustSomeNobody 9y agoThese 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.
- deleted 9y ago[deleted]
- jbob2000 9y agoI'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.
- esrauch 9y agoWhat? Surely the JS you write is embedded in the release build.
- polymeris 9y agoI really need to give Reagent+React native another shot. Last I tried there where still some apparently minor, but annoying issues. That said, even as a clojurescript fan, I wouldn't call this a solution, more like a practical workaround for a deeply flawed dev experience.