Windows 10: Visual Studio Code now the default development environment at Facebook

Brink · Nov 26, 2019

We’re making Visual Studio Code the default development environment at Facebook and teaming with Microsoft to help enhance their remote development extensions in an effort to enable engineers to do remote development at scale.

History

Facebook engineers have written millions of lines of code. 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.

Nuclide began as a set of open-source packages built on top of the Atom editor. We provided our engineers a set of functionality supporting its development workflow and the numerous programming languages used at the company. In 2018, we retired the open source version of Nuclide, but continued to use Nuclide internally.

In late 2018, we announced to our engineers that we would be moving Nuclide to Visual Studio Code. Plenty of development work has been done to migrate the current Nuclide functionality, along with some new features, as internal-facing extensions for Visual Studio Code. Visual Studio Code is now used extensively across the company in beta.

Why Visual Studio Code?

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 we can safely bet our development platform future.

Enhancing the Remote Development Experience

While engineers at Facebook have Visual Studio Code installed locally on laptops, most development is done directly on individually-reserved development servers that live within our data centers. Being able to access code on these servers in a seamless, performant way is critical for productivity.

As Microsoft’s Visual Studio Code team stated when they first released the remote extensions, remote development is an emerging trend. While our use cases may be more advanced than most development teams given our scale, any developer can gain the benefits of remote development:

Work with larger, faster, or more specialized hardware than what’s available on your local machine

Create tailored, dedicated environments for each project’s specific dependencies, without worrying about errors due to mixed or conflicting configurations

Support the flexibility of being able to quickly switch between multiple running development environments without impacting local resources or tool performance

These benefits should be available to any developer, and we at Facebook believe that we can apply our unique expertise in this problem space to help. That’s why today we are excited to share not just our usage of their remote development extensions, but our involvement in helping Microsoft further improve remote development extensions, with a lens on enabling engineers to do remote development at scale with Visual Studio Code.

To help Microsoft enhance its product offering, we have provided input through our experience and expertise supporting remote development for Nuclide. And Microsoft has now created such a robust remoting experience, it has allowed us to move off our own custom solution.

We’re also excited that the remote development capabilities added by Microsoft are available as extensions for anyone using Visual Studio Code.

Moving Forward

Given the scale of development at Facebook, supporting the efficiency and productivity of our engineers is key. Constant work is being done to enable Visual Studio Code to be the IDE of choice inside the company, whether by building extensions or enhancing our current technologies to better support it.

For example, when it comes to code, Facebook is a polyglot. Code is written in Python, C++, Java and in some of our own created languages like Flow, Hack and Reason. Extensions exist to support these languages, which include syntax highlighting, formatters, linters, etc. Flow, for example, has had a Facebook-developed public Visual Studio Code extension since 2015. With Facebook’s internal move to Visual Studio Code, Flow has been in active development, through areas like Language Service Protocol (LSP) improvements, to better ensure the language works great with Visual Studio Code.

Another example is around source control. Facebook uses Mercurial internally as its source control infrastructure. Development work continues on an extension to allow for source control manipulation directly within Visual Studio Code, enabling all of the workflows Facebook developers are comfortable with in order to get their code reviewed and landed.

Visual Studio Code is now an established part of Facebook’s development future. In teaming with Microsoft, we’re looking forward to being part of the community that helps Visual Studio Code continue to be a world class development tool.
Click to expand...

Source: https://developers.facebook.com/blog...e-development/

:)

Brink · Nov 26, 2019

Visual Studio Code now the default development environment at Facebook

We’re making Visual Studio Code the default development environment at Facebook and teaming with Microsoft to help enhance their remote development extensions in an effort to enable engineers to do remote development at scale.

History

Facebook engineers have written millions of lines of code. 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.

Nuclide began as a set of open-source packages built on top of the Atom editor. We provided our engineers a set of functionality supporting its development workflow and the numerous programming languages used at the company. In 2018, we retired the open source version of Nuclide, but continued to use Nuclide internally.

In late 2018, we announced to our engineers that we would be moving Nuclide to Visual Studio Code. Plenty of development work has been done to migrate the current Nuclide functionality, along with some new features, as internal-facing extensions for Visual Studio Code. Visual Studio Code is now used extensively across the company in beta.

Why Visual Studio Code?

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 we can safely bet our development platform future.

Enhancing the Remote Development Experience

While engineers at Facebook have Visual Studio Code installed locally on laptops, most development is done directly on individually-reserved development servers that live within our data centers. Being able to access code on these servers in a seamless, performant way is critical for productivity.

As Microsoft’s Visual Studio Code team stated when they first released the remote extensions, remote development is an emerging trend. While our use cases may be more advanced than most development teams given our scale, any developer can gain the benefits of remote development:

Work with larger, faster, or more specialized hardware than what’s available on your local machine

Create tailored, dedicated environments for each project’s specific dependencies, without worrying about errors due to mixed or conflicting configurations

Support the flexibility of being able to quickly switch between multiple running development environments without impacting local resources or tool performance

These benefits should be available to any developer, and we at Facebook believe that we can apply our unique expertise in this problem space to help. That’s why today we are excited to share not just our usage of their remote development extensions, but our involvement in helping Microsoft further improve remote development extensions, with a lens on enabling engineers to do remote development at scale with Visual Studio Code.

To help Microsoft enhance its product offering, we have provided input through our experience and expertise supporting remote development for Nuclide. And Microsoft has now created such a robust remoting experience, it has allowed us to move off our own custom solution.

We’re also excited that the remote development capabilities added by Microsoft are available as extensions for anyone using Visual Studio Code.

Moving Forward

Given the scale of development at Facebook, supporting the efficiency and productivity of our engineers is key. Constant work is being done to enable Visual Studio Code to be the IDE of choice inside the company, whether by building extensions or enhancing our current technologies to better support it.

For example, when it comes to code, Facebook is a polyglot. Code is written in Python, C++, Java and in some of our own created languages like Flow, Hack and Reason. Extensions exist to support these languages, which include syntax highlighting, formatters, linters, etc. Flow, for example, has had a Facebook-developed public Visual Studio Code extension since 2015. With Facebook’s internal move to Visual Studio Code, Flow has been in active development, through areas like Language Service Protocol (LSP) improvements, to better ensure the language works great with Visual Studio Code.

Another example is around source control. Facebook uses Mercurial internally as its source control infrastructure. Development work continues on an extension to allow for source control manipulation directly within Visual Studio Code, enabling all of the workflows Facebook developers are comfortable with in order to get their code reviewed and landed.

Visual Studio Code is now an established part of Facebook’s development future. In teaming with Microsoft, we’re looking forward to being part of the community that helps Visual Studio Code continue to be a world class development tool.
Click to expand...

Source: https://developers.facebook.com/blog...e-development/

Brink · Nov 26, 2019

Supporting JUnit 5 in Visual Studio Code

After supporting the widely adopted JUnit 4 with the Java Test Runner extension for Visual Studio Code, we’ve received suggestions to add additional test frameworks, like JUnit 5 and TestNG. We’ve added initial support for JUnit 5, including running, debugging test cases as well as test report. Please give us a try and let us know your feedback.

Expression Evaluation based Conditional Break Point

After introducing expression evaluation in our January release for the Java debugger extension, we are bringing the functionality to conditional break points. Now, you can set your breakpoint to break when an expression evaluates to true. We believe this could be a very useful feature when debugging your Java application using Visual Studio Code.

Other Updates

We’ve also added new features to our Java on Visual Studio Code extension lineup, including:

Java Test Runner

Trigger tests from test explorer on different levels

Add command to open log file

Add setting to specify the position of test report

Tomcat

Add several context commands in Tomcat Explorer

Add support for JVM customization and Tomcat server configuration

Add command palette entries for user input

Maven

Add support for auto-update maven project explorer when pom.xml is updated

Try it out

Please don’t hesitate to try Visual Studio Code for your Java development, and let us know your thoughts! Install the Java Extension Pack which includes Language Support for Java by Red Hat, Debugger for Java, Maven, and the Java Test Runner.

Additional resources

If you’re working on Spring Boot, there are also extensions for Spring Boot Tools and Spring Initializr we’ve developed in partnership with Pivotal.

Learn more about Java on Visual Studio Code.

Explore our step by step Java Tutorials on Visual Studio Code.

Xiaokai He,
Program Manager
Click to expand...

Source: Supporting JUnit 5 in Visual Studio Code | The Visual Studio Blog

Brink · Nov 26, 2019

Announcing the Visual Studio Code Installer for Java Developers

It’s been almost 3 years since the first Java language server was developed during a hackathon in a small conference room at Microsoft’s Zurich office with people from Red Hat, IBM, Codenvy and Microsoft, which later became one of the most popular extensions for Visual Studio Code with more than 2.7 million installations. Since then, Visual Studio Code has gone through a thrilling journey and become to the most popular development environments according to Stack Overflow. More and more Java extensions are now available in Visual Studio Code to serve a growing Java community using Visual Studio Code along with their favorite tools and frameworks.

During this journey, we’ve heard many developers ask how to start with Java in Visual Studio Code. As the vibrant Java community expands to include more students and developers from other languages, many new comers struggle with setting up their environment to be able to start coding. To help people get started, we created the Java extension pack to give you the relevant extensions, and also included tutorials with detailed steps in our documentation.

Back in 2018, Microsoft Azure became a Platinum Sponsor of the AdoptOpenJDK project – that just got renewed until June 2020 – and provides a truly vendor neutral, completely free and open source distribution of the JDK (Java Development Kit) based on the OpenJDK project. This was a turning point for us so much we’ve also added a functionality to detect and help developers install a JDK binary in their environments, having AdoptOpenJDK as the recommended distribution. These efforts were encouraging, but got us thinking about more ways we could make it easier to starting coding in Java.

Introducing the Visual Studio Code Java Pack Installer

So today, we’re releasing a special Installer of Visual Studio Code for Java developers. The package can be used as a clean install or an update for existing environment to add Java or Visual Studio Code to your development environment. Once downloaded and opened, it automatically detects if you have the fundamental components in your local development environment, including the JDK, Visual Studio Code and essential Java extensions.

After clicking Install, it will pull the stable versions of those tools from trusted online sources and install them on your system. Once it’s done, you can open Visual Studio Code and start writing and running Java code directly! Below is a short video showing you how to write and run a Hello Worldprogram with Java in Visual Studio Code in less than 1 minute. See more detailed functionality in our tutorial.

The installer is available for download for Windows now while we’re still working on the Mac version. Please have a try and let us know your feedback!

If you’d like to follow the latest of Java on Visual Studio Code, please provide your email with us using the form below. We will send out updates and tips every couple weeks.
Click to expand...

Source: https://devblogs.microsoft.com/visua...ava-installer/

Windows 10: Visual Studio Code now the default development environment at Facebook

Visual Studio Code now the default development environment at Facebook

Visual Studio Code now the default development environment at Facebook

Visual Studio Code now the default development environment at Facebook

Visual Studio Code now the default development environment at Facebook - Similar Threads - Visual Studio Code

New Microsoft Edge browser developer tools for Visual Studio Code

VISUAL STUDIO CODE BLUR...?

Visual Studio Code

visual studio code

Visual Studio now 2019

Announcing the Visual Studio Code Installer for Java Developers

Apache Cordova development lands on Visual Studio Code

Announcing Visual Studio Connected Environment

Visual Studio Code 1.0 now available