Facebook makes Visual Studio Code the default development environment

Facebook recently announced the default use of the Visual Studio Code as an internal development environment.
Last year, Facebook announced that it would stop maintaining its open-source Nuclide/Atom-IDE, as well as related libraries.

Nuclide/Atom-IDE is a feature pack for the Atom editor that interacts with a custom language server through a language server protocol to provide an Atom with a range of IDE-like features. The feature pack consists of various “sub-packages” that are built and released as atom-ide-ui.

Although Facebook does not impose restrictions on what development tools developers use, such as some developers using Vim and Emacs, more developers still use their own Nuclide/Atom-IDE, last year the tool stopped open-source maintenance, but inside Facebook, Developers continue to use it. By the end of the year, Facebook announced to internal developers that they will migrate from Nuclide to Visual Studio Code.

Facebook introduced that in order to use the current Nuclide features and new features like an internal extension of Visual Studio Code, Facebook has done a lot of development work. At present, a large number of developers within the company have used the Visual Studio Code.

Now, even further, the official announcement of Visual Studio Code as Facebook’s default development environment , and cooperation with Microsoft to help enhance its remote development extensions, enabling developers to carry out large-scale remote development.

Facebook writes:

“Visual Studio Code is a very popular development tool, with great investment and support from Microsoft and the open source community. It runs on macOS, Windows, and Linux, and has a robust and well-defined extension API that enables us to continue building the important capabilities required for the large-scale development that is done at the company. Visual Studio Code is a platform on which we can safely bet our development platform future.”