During the first keynote at the BUILD conference in San Francisco, Microsoft crossed a line that many believed would never be crossed with the unveiling of Visual Studio Code (VSC). For the first time, Microsoft is providing a developer productivity tool to users whether or not they are running Windows as their client OS, which continues the trend started by the Azure team of embracing technology even when it’s not invented by Microsoft.
This new tool has installers for Windows, Linux and OS X, and the download site has a nice feature in that it will offer you the right version based on the OS you are browsing from while also giving you links to grab the other versions.
(Related: More news out of Build)
To succeed, developers not on Windows have to be among those who use the tool, and early indicators are positive. After the first day of availability, more than half the downloads of Visual Studio Code were by users not running Windows. This product’s introduction means that developers from all platforms can benefit from great productivity features long enjoyed by Visual Studio users, like IntelliSense, autocomplete and debugging in a super-fast and very lightweight editing tool.
VSC is an editor with IDE aspirations and some killer features out of the box. Editors and IDEs both let you write your code, but they provide different experiences along the spectrum, and each end of that spectrum has its own strengths. Microsoft has designed VSC to be an editor with some of the best features from the IDE while not ruining the advantages of being an editor.
In the vehicular world, the SUV is just such a hybrid because it has the comforts of a car with the height, storage and versatility of a light truck. These kinds of tradeoffs are evidenced by the fact that VSC deals at the file and folder level rather than having solutions like Visual Studio, but it supports project context for working with solutions created by Visual Studio or checked into Team Foundation Server.
While I was quite impressed by the mere existence of such a tool from Microsoft, I feared that it might be a one-and-done release, which would greatly dampen the usefulness for developers in the long run. I asked whether Visual Studio Code would get updates as new versions of the Visual Studio suite were released, or if it was code complete. The answer was far better than expected because it turns out that there is a team for VSC, and updates will be regular and ongoing; specifically, every three weeks was the stated goal for updates to be pushed out.