spicyj

I manage the React team at Facebook. Only a couple of us have been on the team since before Dan, and I don’t think anyone resents his public persona. Quite to the contrary – Dan does a great job representing us. :)

At Facebook most of our thousands of web devs use Nuclide for remote editing on a repo with hundreds of thousands (or millions) of files and it works as advertised. We don’t use NFS though; all the repo checkouts are on disk on the remote machine.

I don’t understand what requires a web view here. You should be able to do anything another app can do (especially if you’re willing to write some custom native code, which I assume you are if you’re considering full native).

Do you mean the big green button? You can usually click the first track to start playing in order.

Use Prettier and never look back.

Browser extension? I know Millenials to Snake People caused this at one point.

No. I work at Facebook, and we don’t block any sites except ones with malware.

Yes, making the source easy to understand is definitely valuable (even if only for our own team's understanding).

I believe Django's "functionality/(API surface)" quotient is still much lower than React's, which means it's easier to make the source useful to a newcomer.

Thanks!

* Links to source: I use these frequently in other libraries, but I don't think this would be as useful for React, because we tend to have just a few functions each with a complicated implementation (vs programming stdlibs or other frameworks where many methods are on the order of 10-100 lines calling other public functions). Also our implementation isn't that easy to understand. I wonder if you had a particular use case in mind? * Linked method names: Good idea. * Version switcher: We've thought about this and will probably add it at some point.

I work on React. We've worked really hard on our docs, so it would be helpful to know what you don't like about them so we can improve.

Likely yes.

Certainly there are downsides to any setup, but due to React Native's large ambitions I'm unsure if it could have ever been created by an independent community. There is a lot of work that goes into it and the abundant availability of complex real-world problems (to a greater extent than I've seen anywhere else) spurred by this setup pushes React Native to be a more capable project.

Yes, we'll likely support some form of this. It's important for controlled native components too (ex: text inputs).

Most of the code is in the repo in React/Fabric/ and ReactCommon/fabric/ but unfortunately it's not runnable yet due to some missing dependencies that aren't currently in the open source repo.