> We’re making Visual Studio Code the default development environment at Facebook
IDE choice is a highly personal thing. This sounds awful.
Facebook and Microsoft Partner on Remote Development
11–20 of 145 posts
Re: Facebook and Microsoft Partner on Remote Development
#12> We’re making Visual Studio Code the default development environment at Facebook IDE choice is a highly personal thing. This sounds awful.
It's the _default_, as they say in the article:
> There is no mandated development environment. Some developers use vim. Some use Emacs. And even more engineers use our internal, unified development environment called Nuclide.
Re: Facebook and Microsoft Partner on Remote Development
#13> We’re making Visual Studio Code the default development environment at Facebook IDE choice is a highly personal thing. This sounds awful.
Having a recommended/default IDE is not the same thing as forcing everyone to use it.
Re: Facebook and Microsoft Partner on Remote Development
#14> We’re making Visual Studio Code the default development environment at Facebook IDE choice is a highly personal thing. This sounds awful.
In every place I've been, the IDE choice has been more of a team decision, configuration was personal (some short-cuts, colors, etc). Too much time went into the build environment and other development tools for us, plus if you wanted someone to come in and help (short term pair programming), you need to be on the same page.
Re: Facebook and Microsoft Partner on Remote Development
#15Remote development via TRAMP is the number 1 reason I'm stuck with Emacs. More support via other editors is always appreciated.
Re: Facebook and Microsoft Partner on Remote Development
#16Earlier quoted context omitted.
Disclaimer: Work at Facebook Not really sure what you are implying with the 'Big Brother' comment. The remote development servers are only used for writing/debugging code and not for other daily tasks. Even if they are tracking what tools/functions I am using on the server, what does that matter? Personally, I have found remote development awesome because it enables engineers to start contributing to a huge product i…
People don't like being tracked and Facebook has a long history of being deceptive around how and when it tracks people. Facebook also has a long history of selling the data it collects as a result of tracking even when the people being tracked try as they might to opt out. Hence the "big brother" reference. Frankly, I was/am a little leary of how Facebook might be "improving" the MSVSC Remote Development pack since…
As an employee working on a corporate device everything will be tracked anyways, this is the most tin-foil take ever.
Your latter concern is at least a reasonable one, but it should all be open source anyways? Not that any of us have the time to audit everything. I doubt Microsoft is going to allow anything nefarious...
Re: Facebook and Microsoft Partner on Remote Development
#17Very happy about this move. Nuclide’s remote development capabilities were way above anything else I’ve tried (Sublime, IntelliJ Ultimate, VSCode, remote SSH mounts, etc).
It’s the only solution I’ve found that really allows you to browse the remote filesystem as smoothly as you would with your local drive (including when you’re also changing the remote files outside the IDE), degrade functionality as needed when the connection isn’t great (using caching appropriately), and immediately recover when it comes back. The only cost to pay was a bit of setup server-side (installing watchman and opening a port, if I remember correctly). I really hope they can bring the VSCode experience to the same level!
Re: Facebook and Microsoft Partner on Remote Development
#18> We’re making Visual Studio Code the default development environment at Facebook IDE choice is a highly personal thing. This sounds awful.
Default is definitely different than mandated. Facebook provides engineers a ton of freedom for their development environment.
There are many at FB where we would have to pry vim or emacs out of their hands, and, even then, we would not be successful. :-)
Re: Facebook and Microsoft Partner on Remote Development
#19I’m disappointed this wasn’t really about remote workers but about remote development as in code doesn’t live on the machine. That said, remote development tends to be awful, and more tools could be helpful if it’s not specific to a FBs particular implementation of remote dev shards. Learning that at Facebook you don’t develop things locally and likely are on a box with all sorts of things tracking your usage and acc…
Disclaimer: Work at Facebook Not really sure what you are implying with the 'Big Brother' comment. The remote development servers are only used for writing/debugging code and not for other daily tasks. Even if they are tracking what tools/functions I am using on the server, what does that matter? Personally, I have found remote development awesome because it enables engineers to start contributing to a huge product i…
[deleted]
Re: Facebook and Microsoft Partner on Remote Development
#20Remote development via TRAMP is the number 1 reason I'm stuck with Emacs. More support via other editors is always appreciated.
[deleted]