Hacker News Reader

Comment by axemclion | Hacker News Reader

This is incorrect. Here is a response from Tim, who manages the React Native team - https://twitter.com/yungsters/status/989361665752748033

Also, here is a list of all the things that our team has been working on with React Native - https://www.youtube.com/watch?v=1hvQ8p8q0a0

View on HN

That tweet was a month ago. This change could have been more recent than that.

Nothing has changed. Multiple people have directly rebutted him on the twitter thread. This was FUD plain and simple.

As someone who manages a team at a large corp that uses react native and ships a successful project things have definitely changed. It feels like Facebook has lost interest.

- the android debugger has been broken for months (it opens to the wrong url, delta patches also broke source maps). No one at Facebook cares. Do they not use the debugger?

- pull requests have stopped being merged. We have FIVE outstanding pull requests fixing bugs as old as ones ignored by Facebook from 2016. No one will reply or merge them anymore. We've been told to just create a fork on GitHub for our project. Apparently that's what every serious RN user does because Facebook doesn't really care about it anymore.

- they have a bot who auto closes bugs somewhat randomly. For example an old bug that Facebook ignored with hundreds of comments gets closed for "inactivity", but it's not active because folks all complained and now they're just waiting for someone to fix it.

So it all combines to a situation where the platform is buggy, but you can't get fixes merged, and filing bugs is largely a waste of time since all it gets is auto replies from the bot and "me too" responses from others.

We really like RN, it helped us ship fast at first, but Facebook absolutely seems to have lost interest in it and in having a community around it.

I understand what you are saying, since I too am upset about many issues being closed without being fixed. I come across them when doing searches for various problems with RN. It's the same with Flow, the Javascript type checker, only that there it seems like nobody from the dev team even cares about the Github repo and the huge list of open issues (hey, at least they don't close them all automatically by bot).

On the other hand, the commit history seems pretty active - and that's an understatement: https://github.com/facebook/react-native/commits/master (same for Flow)

I think the commit history says more than (auto-)closed issues. They may not share our priorities but they keep working on the project pretty actively.

I work on React so I have some context on this.

I’m sorry it’s frustrating but it’s not at all because FB lost interest. In fact it’s the opposite. We’re making pretty big bets on complex core architectural improvements to RN, and the team is heads down busy with these core changes. Unfortunately it does mean that PRs and external contributions get less attention until those core improvements are done.

If there’s a specific PR that’s blocking you please ping me in DM on Twitter and I’ll try to get somebody to review it.

Cheers.

I use RN, interested in these architectural improvements being done. Any link to an issue or description of these, or a short explanation?

We’ll post more when it’s closer to being production-ready. But TLDR is that we’re making improvements to the threading model and interop with native code.

Reply on news.ycombinator.com