4 ms·

So, does this mean Facebook is adopting VS Code?

• pbalau 8y ago
  This can mean vscode gets remote code editing. That's nice
  • bdcravens 8y ago
    There's already multiple extensions that support this.
    • reaperducer 8y ago
      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.
      • evv 8y ago
        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.
      • borzale 8y ago
        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.
      • catacombs 8y ago
        Use emacs or vim. They work right out of the box.
    • pbalau 8y ago
      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)
      • akhilcacharya 8y ago
        Why not use FUSE?
        • pbalau 8y ago
          Care to elaborate? A link works :)
          • ricketycricket 8y ago
            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 https://github.com/libfuse/sshfs
            • pbalau 8y ago
              Thanks. I tried libfuse in the past and I reached the same conclusion.
            • akhilcacharya 8y ago
              I use https://osxfuse.github.io/ 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.
        • imbiased 8y ago
          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.
          • akhilcacharya 8y ago
            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.
• bdcravens 8y ago
  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.
• underwater 8y ago
  Apparently not: https://mobile.twitter.com/amasad/status/1072930703065501696 https://mobile.twitter.com/amasad/status/1072930703065501696
  • pbalau 8y ago
    Damn... :(
  • amasad 8y ago
    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.
    • vjeux 8y ago
      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.