Facebook retires Nuclide Atom extension • Hacker News Board

Re: Facebook retires Nuclide Atom extension

#41

Post by vjeux » Wed, Dec 12, 2018, 9:53 PM UTC

amasad wrote: post #28

underwater wrote: post #12

Earlier quoted context omitted.

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.

Nuclide has always had a ton of value for Facebook itself as we could build a lot of Facebook-specific integrations and ship a new version to all the developers every week. It's now the most used editor at Facebook.

This announcement is about the open source version of Nuclide, which has never received a lot of love and didn't have a lot of adoption.

Re: Facebook retires Nuclide Atom extension

#42

Post by lucasmullens » Wed, Dec 12, 2018, 9:58 PM UTC

dizzy3gg wrote: post #27

sophiebits wrote: post #19

Earlier quoted context omitted.

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?

VSCode is in particular great at TypeScript, in part because it's a Microsoft language and Microsoft IDE.

Re: Facebook retires Nuclide Atom extension

#43

Post by jtolds » Wed, Dec 12, 2018, 10:14 PM UTC

Wait, so with Github taking complete responsibility for Atom, that means Atom and VSCode are now ultimately run/sponsored by the same company (MS)?

Re: Facebook retires Nuclide Atom extension

#44

Post by underwater » Wed, Dec 12, 2018, 10:20 PM UTC

sophiebits wrote: post #20

underwater wrote: post #11

Earlier quoted context omitted.

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.

No, our priorities for React and other libraries are not tied directly to internal app metrics.

Good to hear that's still the case. I'm particularly worried about Flow, given that it's generally not trending well against TypeScript in terms of adoption, and because the team has never been super-engaged with the open source community. Would Facebook consider publicly clarifying intent to support less successful projects into the next 12 to 24 months?

Re: Facebook retires Nuclide Atom extension

#45

Post by akhilcacharya » Wed, Dec 12, 2018, 11:05 PM UTC

imbiased wrote: post #33

akhilcacharya wrote: post #22

Earlier quoted context omitted.

Why not use FUSE?

This would mean things (compile, run, debug, etc) would be done on the local machine, not on the remote one. Not to mention the network lag if a huge codebase.

What I usually just do is open up a terminal in the FUSE mounted directory and an SSH session in another tab. Run everything on the remote machine and make edits on the local machine using any editor I want.

RE: building, compiling without login etc - I have a bunch of aliases that let me do that remotely with ssh. You're still "logging in" but don't need to deal with anything major.

Re: Facebook retires Nuclide Atom extension

#46

Post by akhilcacharya » Wed, Dec 12, 2018, 11:05 PM UTC

ricketycricket wrote: post #30

pbalau wrote: post #24

Earlier quoted context omitted.

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

I use https://osxfuse.github.io/

Big file changes are never going to be fast (even doing git operations is pretty slow) but remote interaction can be done via ssh in another tab.

Re: Facebook retires Nuclide Atom extension

#47

Post by Mistri » Wed, Dec 12, 2018, 11:09 PM UTC

jtolds wrote: post #43

Wait, so with Github taking complete responsibility for Atom, that means Atom and VSCode are now ultimately run/sponsored by the same company (MS)?

Yes, but under very different management.

Re: Facebook retires Nuclide Atom extension

#48

Post by straws » Wed, Dec 12, 2018, 11:13 PM UTC

imbiased wrote: post #6

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/

It would seem that https://github.com/atom/atom-languageclient is still under active development. Hopefully this means that the core Atom team will continue to work on language server features.

Re: Facebook retires Nuclide Atom extension

#49

Post by [deleted] » Thu, Dec 13, 2018, 12:12 AM UTC

straws wrote: post #48

imbiased wrote: post #6

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/

It would seem that https://github.com/atom/atom-languageclient is still under active development. Hopefully this means that the core Atom team will continue to work on language server features.

[deleted]

Re: Facebook retires Nuclide Atom extension

#50

Post by mraison » Thu, Dec 13, 2018, 12:23 AM UTC

I will really miss the remote development experience. It didn't get a lot of visibility because Nuclide's scope was much broader. It was also a pain to setup (compiling Watchman from source on Linux servers...) but after the initial setup it was way better than anything else out there (FUSE mounts, rmate, etc). Hopefully VSCode will get there soon.