react-native

People (including a team member of mine) are still commenting on https://github.com/facebook/react-native/issues/8475 which has been iceboxed and never re-opened. Same problem, which made the RN team seem very unreceptive. Indeed, I think it's worth a shot to see if the metro team is more receptive. Thanks for the suggestion.

Primarily since it's been an issue for over a year, reported here https://github.com/facebook/react-native/issues/8475 as well, with no help from the RN team. > Also, that doesn't sound like a Babel issue, as I've compiled JS files that were several MB before without taking an unreasonable amount of time. The error is specifically that transformation of the JS times out, so it very much appears to be a babel issue. It might be something specific to the RN preset though.

This is strictly for transforming JS. It has existed for over a year, here https://github.com/facebook/react-native/issues/8475 as well. It's certainly possible that the babel team was never aware of it, but I'd imagine this has to do with the seemingly exponential growth of transformation time per source KB.

In my experience, babel is the single most unreliable and unusable piece of the build machine. The issue to blame is https://github.com/facebook/react-native/issues/12590 which has been "iceboxed" and not fixed. In short, I have to patch metro each build, to increase the time it waits before killing babel, since the 5 minute timeout simply doesn't cut it. Debug builds would take over 30m to transform with babel.

If I'm not mistaken, https://github.com/facebook/react-native/commit/b58207e61fcb... enables the new implementation in RN. So it'll be in React Native 0.49.

Here's the problem with that type of snark; when you're wrong it's really bad for you. You are responding to a question about react NATIVE, which still has the patent grenade (see below). https://github.com/facebook/react-native/blob/master/PATENTS

So which FB project still have a BSD+patents license. I count: * ReasonML - https://github.com/facebook/reason/blob/master/PATENTS.txt * GraphQL - https://github.com/graphql/graphql-js/blob/master/PATENTS * react-native - https://github.com/facebook/react-native/blob/master/PATENTS * PlanOut - https://github.com/facebook/planout/blob/master/PATENTS * Flow - https://github.com/facebook/flow/blob/master/PATENTS * Haxl - https://github.com/facebook/Haxl/blob/master/PATENTS * Flux - https://github.com/facebook/flux/blob/master/PATENTS Just a few that I found.. Please reply if you know more project that are still BSD+PATENTS licensed.

I don't regret adopting React Native for a big project, since I think we've been able to prototype and iterate much more quickly than we would if writing in Swift or Java, and it's enabled us to get webdevs up to speed on mobile without having to teach them entirely new programming paradigms and languages. But... RN still has huge blocking bugs like this one: https://github.com/facebook/react-native/issues/14209 that seem to pop up at random times, and not always for the same developers. I thought yarn would solve some of these issues, but they still kill our dev team and halt all work every once in a while. And it's annoying as heck.

Interesting. Then why does everything look and behave so poorly? And if it's so easy, why doesn't React Native ship with at least every default native control wrapped? Edit: what a beautiful example of what I'm talking about: https://github.com/facebook/react-native/issues/371

I work with both native iOS and React Native on daily basis. Both had their own (dis)advantages and it's hard to have a definite answer on which is better. It all depends on the nature of the app you want to build, your budget and trade-offs you are willing to take. RN is moving fast and has improved a lot in the recent months but still has some pain points: - If you want to build a chat app, forget about well working sticky text input. (https://github.com/facebook/react-native/issues/371) - All the dev time you have saved with hot reloading will be lost if you hit the infamous 4968 (https://github.com/facebook/react-native/issues/4968) - Multithreading, but that has been covered in other comments. If you're obsessed about buttery smooth UI you'll have some unpleasant time. Also : - I find RN's ecosystem feeble and don't trust packages. T

Thanks. Is that's really what's happening with React Native's built-in button though? https://github.com/facebook/react-native/blob/master/Librari... if (color && Platform.OS === 'ios') { textStyles.push({color: color}); } else if (color) { buttonStyles.push({backgroundColor: color}); } Looks like they are just styling them differently to make them look like system default.

Definitely interested in seeing how Flutter progresses, IMO it has the optimal architecture for developing native, x-plat iOS/Android UI (https://flutter.io/technical-overview/): - High perf Skia based UI for pixel perfect rendering and high-level Material design widgets - React inspired, productive development model - Fast dev/iteration cycles with hot reloading - Productive and high-performance Dart language, natively compiled (AOT on iOS) - Enable native interop with underlying iOS/Android APIs - Actively developed by Google Overall I think it has a superior architecture to React Native where it will enable higher-perf native iOS/Android Apps in a single code-base but still enables a productive development model with Instant UI updates and hot reloading. I've done Java and Kotlin Android Apps as well as Obj-C and Swi