News for hackers. Stuff that matters.
Re:Facebook retires Nuclide Atom extension by philosopherlawr on Wednesday December 12, 2018 @03:24PM (#18667421)
So, does this mean Facebook is adopting VS Code?
Re:Facebook retires Nuclide Atom extension by underwater on Wednesday December 12, 2018 @03:42PM (#18667562)
Re:Facebook retires Nuclide Atom extension by amasad on Wednesday December 12, 2018 @04:25PM (#18667893)
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 by vjeux on Wednesday December 12, 2018 @04:53PM (#18668071)
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 by pbalau on Wednesday December 12, 2018 @03:51PM (#18667637)
Damn... :(
Re:Facebook retires Nuclide Atom extension by bdcravens on Wednesday December 12, 2018 @03:31PM (#18667476)
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 by pbalau on Wednesday December 12, 2018 @03:28PM (#18667450)
This can mean vscode gets remote code editing. That's nice
Re:Facebook retires Nuclide Atom extension by bdcravens on Wednesday December 12, 2018 @03:34PM (#18667502)
There's already multiple extensions that support this.
Re:Facebook retires Nuclide Atom extension by pbalau on Wednesday December 12, 2018 @03:43PM (#18667571)
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)

Re:Facebook retires Nuclide Atom extension by akhilcacharya on Wednesday December 12, 2018 @04:12PM (#18667810)
Why not use FUSE?
Re:Facebook retires Nuclide Atom extension by imbiased on Wednesday December 12, 2018 @04:33PM (#18667946)
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.
Re:Facebook retires Nuclide Atom extension by akhilcacharya on Wednesday December 12, 2018 @06:05PM (#18668503)
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 by nikitakit on Wednesday December 12, 2018 @09:29PM (#18669445)
I've found that FUSE/sshfs (at least on Mac) doesn't survive network reconnects. Switching WiFi networks, or even having the computer go to sleep, is enough to put it in a state where it can neither be used nor unmounted cleanly.
Re:Facebook retires Nuclide Atom extension by pbalau on Wednesday December 12, 2018 @04:16PM (#18667839)
Care to elaborate? A link works :)
Re:Facebook retires Nuclide Atom extension by ricketycricket on Wednesday December 12, 2018 @04:30PM (#18667921)
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

Re:Facebook retires Nuclide Atom extension by akhilcacharya on Wednesday December 12, 2018 @06:05PM (#18668504)
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 by pbalau on Wednesday December 12, 2018 @04:46PM (#18668037)
Thanks. I tried libfuse in the past and I reached the same conclusion.
Re:Facebook retires Nuclide Atom extension by reaperducer on Wednesday December 12, 2018 @03:42PM (#18667563)
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.
Re:Facebook retires Nuclide Atom extension by evv on Wednesday December 12, 2018 @04:07PM (#18667780)
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 by borzale on Wednesday December 12, 2018 @04:18PM (#18667861)
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 by catacombs on Wednesday December 12, 2018 @10:01PM (#18669560)
Use emacs or vim. They work right out of the box.