Reply from Facebook about "What do you dislike about React Native?" #104
More than two months ago in #64 we asked "What do you dislike about React Native?". We have since made progress at Facebook on our incremental rewrite of React Native, via Fabric (#4) and TurboModules (#40), and started deprecating and removing many modules as part of the Lean Core effort. We reduced the number of open pull requests to ~70, compared to ~280 in December, by merging most of them and closing only the ones that weren't applicable any longer. Simultaneously, the average number of Pull Requests that get opened against React Native increased from ~3.5 to ~8 per day.
We are finally done replying to all of the issues that were mentioned in #64. Please read
Upgrading requires a lot (too much?) effort #
Upgrading from one version to another is hard and requires a lot of work. Especially when you have fallen a couple of versions behind and have to manually upgrade from yours to the latest version by version.
Debugging exceptions #
I dislike that it's often not really easy to find the root cause of an exception. The stack trace in Chrome debugger console often leads to ExceptionManager and not the original place, which lead to time consuming debugging. Using componentDidCatch does not really help.
Surprisingly, when we add a
Support of React Native team #
Would be nice to see a bigger involvement from react-native team to the community.
Performance, performance, performance #
First of all, I am an Android user. I don't use an old phone, I use Pixel 2 which is one of the top game. It's still noticeable when an app is in greenfield or not. Mostly, startup time. Startup time is quite crucial difference between pure native and RN. Not only when you open the app but for deep linking too. Imagine clicking an Android widget that opens the app, in RN the waiting time is just slow. You can mask that with a splash screen, brownfield apps, etc. But it's just a workaround. The feeling is not "native".
One of the problems on this has been navigation too. I think the problem here is that Facebook probably just uses its own navigation system (native app that has some RN views). So they don't really need to help or invest in a common solution. That is a pity. When you develop an Android app or an iOS app, you don't need to care of navigation performance (mostly). It just works.
Metro follow symlinks #
Currently Metro does not follow symlinks, which makes it harder for the community to:
The solution to lots of problems is
The text was updated successfully, but these errors were encountered:
Great! Any chance of having more web polyfills (like a proper
I can help if necessary.
I really don't like your's update Flow.js model!
Recently flow.js improve support React and make many breaking changes
you can see how much has been added
We shared a progress update in our latest blog post here: https://facebook.github.io/react-native/blog/2019/06/12/react-native-open-source-update and simultaneously started a new issue to request for feedback on React Native: #134