I went in for an interview recently for the react core team and the guy who interviewed me said Facebook was trying to edge away from open source. He mentioned it’s not worth it to them as much as it was before. Too much to maintain.
Facebook retires Nuclide Atom extension
11–20 of 67 posts
Re: Facebook retires Nuclide Atom extension
#12So, does this mean Facebook is adopting VS Code?
Re: Facebook retires Nuclide Atom extension
#13Earlier quoted context omitted.
This can mean vscode gets remote code editing. That's nice
There's already multiple extensions that support this.
Re: Facebook retires Nuclide Atom extension
#14Earlier quoted context omitted.
This can mean vscode gets remote code editing. That's nice
There's already multiple extensions that support this.
What I mean by remote code editing is not logging in the remote machine and use something like rmate, but having the entire project available in your ide and being able to edit, do source control stuff, even build and debug without logging on that machine. Nuclide provided all that (for FB dev servers)
Re: Facebook retires Nuclide Atom extension
#15Re: Facebook retires Nuclide Atom extension
#16Re: Facebook retires Nuclide Atom extension
#17I went in for an interview recently for the react core team and the guy who interviewed me said Facebook was trying to edge away from open source. He mentioned it’s not worth it to them as much as it was before. Too much to maintain.
Facebook has not made any meaningful changes in its OSS strategy. It has always been the case that it takes energy to maintain projects in OSS and that for projects that are not used much by external folks it might not be worth the energy.
However, we are continuing to develop React with OSS as a first class citizen, doubling down on our investment in React Native in open source, and likely to still open source new projects as they make sense.
Re: Facebook retires Nuclide Atom extension
#18I went in for an interview recently for the react core team and the guy who interviewed me said Facebook was trying to edge away from open source. He mentioned it’s not worth it to them as much as it was before. Too much to maintain.
I manage the React Core team. That sounds wrong to me. Facebook has not made any meaningful changes in its OSS strategy. It has always been the case that it takes energy to maintain projects in OSS and that for projects that are not used much by external folks it might not be worth the energy. However, we are continuing to develop React with OSS as a first class citizen, doubling down on our investment in React Nativ…
Re: Facebook retires Nuclide Atom extension
#19Earlier quoted context omitted.
I manage the React Core team. That sounds wrong to me. Facebook has not made any meaningful changes in its OSS strategy. It has always been the case that it takes energy to maintain projects in OSS and that for projects that are not used much by external folks it might not be worth the energy. However, we are continuing to develop React with OSS as a first class citizen, doubling down on our investment in React Nativ…
So is there an "official" editor/IDE for React now? What's mostly used by the React team?
VSCode has particularly good integration with TypeScript, so perhaps choose it if you are otherwise undecided.
Re: Facebook retires Nuclide Atom extension
#20I went in for an interview recently for the react core team and the guy who interviewed me said Facebook was trying to edge away from open source. He mentioned it’s not worth it to them as much as it was before. Too much to maintain.
I believe that their internal organisation has changed too. Product Infrastructure, who open sourced GraphQL, React, Relay, Flow, etc. was rolled into a core team, whose priorities are undoubtedly tied directly to internal a app metrics.