Facebook retires Nuclide Atom extension

#1

Post by malmaud » Wed, Dec 12, 2018, 7:16 PM UTC

Facebook retires Nuclide Atom extension
blog.atom.io

Re: Facebook retires Nuclide Atom extension

#2

Post by philosopherlawr » Wed, Dec 12, 2018, 8:24 PM UTC

So, does this mean Facebook is adopting VS Code?

Re: Facebook retires Nuclide Atom extension

#3

Post by pbalau » Wed, Dec 12, 2018, 8:28 PM UTC

philosopherlawr wrote: post #2

So, does this mean Facebook is adopting VS Code?

This can mean vscode gets remote code editing. That's nice

Re: Facebook retires Nuclide Atom extension

#4

Post by bdcravens » Wed, Dec 12, 2018, 8:31 PM UTC

philosopherlawr wrote: post #2

So, does this mean Facebook is adopting VS Code?

Not necessarily. It may be that the current ecosystem works as well or better than Nuclide did, so there's no longer a positive value proposition there for continuing.

Re: Facebook retires Nuclide Atom extension

#5

Post by anontechworker » Wed, Dec 12, 2018, 8:32 PM UTC

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.

Re: Facebook retires Nuclide Atom extension

#6

Post by imbiased » Wed, Dec 12, 2018, 8:33 PM UTC

Can you update the title to add Atom IDE?

Perhaps more important than Nuclide itself are the Atom IDE extensions which are also being retired. https://ide.atom.io/

Re: Facebook retires Nuclide Atom extension

#7

Post by bdcravens » Wed, Dec 12, 2018, 8:34 PM UTC

pbalau wrote: post #3

philosopherlawr wrote: post #2

So, does this mean Facebook is adopting VS Code?

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

#8

Post by imbiased » Wed, Dec 12, 2018, 8:35 PM UTC

anontechworker wrote: post #5

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.

A shame, in an ideal world there would be the benefit of outside contributions that made less internal work needed, so overall would be a win for Facebook. But probably this is related to Atom itself being taken over by VSCode, the number of users (and maybe contributors) appears to be going down. I wonder if Atom Xray will ever come out https://github.com/atom/xray

Re: Facebook retires Nuclide Atom extension

#9

Post by booleandilemma » Wed, Dec 12, 2018, 8:38 PM UTC

anontechworker wrote: post #5

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.

It seems FB is underestimating the PR value that supporting open source brings. Microsoft, on the other hand, seems to understand it well.

Re: Facebook retires Nuclide Atom extension

#10

Post by bdcravens » Wed, Dec 12, 2018, 8:39 PM UTC

anontechworker wrote: post #5

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.

Perfectly rational. Obviously they want to keep React closer to the chest as that directly impacts their core product. Things on the periphery are probably better left to others; I'd imagine it's more effective to donate dollars than hours for those kinds of projects.