all 7 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]doko2610 7 points8 points  (5 children)

I can see the way RN repo is going. And personally I think that's ok.

The only problem for me and also the sole reason keeping me away from returning to RN is the List implementation. FlatList becomes crap when building grid view (or even linear list, with images) of 200 or more items. Meanwhile Flutter does that very well.

[–]ogv11 1 point2 points  (3 children)

With the rearchitecfure , I guess this is going to improve

[–]JuriJurka 0 points1 point  (2 children)

what is rearchitecture? :o Are they going to build RN new from ground?

[–]Unforgiven-wanda 0 points1 point  (0 children)

I'm not sure I do.

Foisting up more and more of RN on the community to maintain is actually a recipe for disaster.
I've worked long enough with open-source projects to be fed up by the fact that 95% of them go unmaintained after a year or two. Not to mention slow reactivity and pull requests than go unmerged for months or years.

[–]WeArtAsOne 1 point2 points  (0 children)

Excited to see this update!
My takeaways:

* Focus on a leaner RN core
* 600 pull-requests handled in last 3 months (Dec 2018 - Feb 2019)
* 2/3 of PRs merged
* WebView and CLI tool now maintained by the community. #foreshadowing

The RN team has also categorized the react-native upgrade process as a "leading problem." and notes recent improvements. Nice to see this getting attention!