Live data from Hacker News

Facebook retires Nuclide Atom extension

blog.atom.io

21–30 of 67 posts

Re: Facebook retires Nuclide Atom extension

#21

Earlier quoted context omitted.

There's already multiple extensions that support this.

One of the reasons I don't use VSCode is because I just want to work, not spend a week hunting down extensions for features that should be included.

What do you use instead?

Personally I've found that VSCode has great out-of-the-box functionality for front-end/JS development, in comparison to Atom and SublimeText.

Re: Facebook retires Nuclide Atom extension

#22
post #14

Earlier quoted context omitted.

There's already multiple extensions that support this.

Wanted to edit my comment, too late... 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)

Why not use FUSE?

Re: Facebook retires Nuclide Atom extension

#23

Earlier quoted context omitted.

So is there an "official" editor/IDE for React now? What's mostly used by the React team?

I think people on our team use VSCode, Sublime Text, and Vim. Almost all editors these days have good support for React, so we don't have any official one (nor do we feel the need to). VSCode has particularly good integration with TypeScript, so perhaps choose it if you are otherwise undecided.

Thanks for sharing. Curious if Nuclide is omitted because it's a given, or isn't used much internally now (https://mobile.twitter.com/amasad/status/1072930703065501696)

Re: Facebook retires Nuclide Atom extension

#24
post #14

Earlier quoted context omitted.

Wanted to edit my comment, too late... 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)

Why not use FUSE?

Care to elaborate? A link works :)

Re: Facebook retires Nuclide Atom extension

#25

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.

It's an IDE whose only existence was due to their _wildly_ popular open source software, so they seem to understand it pretty well...

Re: Facebook retires Nuclide Atom extension

#26

Earlier quoted context omitted.

There's already multiple extensions that support this.

One of the reasons I don't use VSCode is because I just want to work, not spend a week hunting down extensions for features that should be included.

That's interesting, because it's the reason I do use vscode. I just want to work and it takes a whole of 5 minutes to setup and get going, on basically any OS I want. It can't be light weight and also include every feature everyone wants.

Re: Facebook retires Nuclide Atom extension

#27

Earlier quoted context omitted.

So is there an "official" editor/IDE for React now? What's mostly used by the React team?

I think people on our team use VSCode, Sublime Text, and Vim. Almost all editors these days have good support for React, so we don't have any official one (nor do we feel the need to). VSCode has particularly good integration with TypeScript, so perhaps choose it if you are otherwise undecided.

Building an app with react native at the moment, the team uses VSCode & WebStorm. Why would TypeScript be the deciding factor?

Re: Facebook retires Nuclide Atom extension

#28

So, does this mean Facebook is adopting VS Code?

Apparently not: https://mobile.twitter.com/amasad/status/1072930703065501696

Nuclide replaced FBIDE, the internal pre-setup web IDE that Facebook used. Having a pre-setup environment is a huge productivity boost:

- dev env onboarding takes a minute instead of a week

- employees can code "on the go"

So predictably, if they get rid of Nuclide there needs to be an alternative and doubtful they've built something new because... why.

Re: Facebook retires Nuclide Atom extension

#29

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.

I’m surprised to see an engineer admit this during an interview (assuming it is true, sophiebits has mentioned that it she doesn’t agree with this). Presumably this is the time when you talk about how much cool open source work you do?

Re: Facebook retires Nuclide Atom extension

#30
post #24

Earlier quoted context omitted.

Why not use FUSE?

Care to elaborate? A link works :)

They probably are referring to something like SSHFS that allows you to mount remote filesystems over SSH using FUSE. I have tried this and it doesn't work well.

https://github.com/libfuse/sshfs

Post reply on HN