Microsoft code editor Visual Studio Code (VS Code) is just five years old but the developer tool has gained impressive adoption with the world's developer population.
Julia Liuson, corporate vice president of Microsoft's developer division, reckons the growth in VS Code adoption has come because people beyond professional developers increasingly finding the need to use the editor.
"Traditionally, we only saw professional developers but we're seeing a really broad set of users – people doing DevOps, people doing IT administration, we see lots of students using the tools," Liuson told ZDNet.
Given it's a text editor, people don't even need to know how to code to make use of the software. Even some journalists are using VS Code to write stories, according to Liuson.
"The strategy for VS Code is really to support our any, any, any strategy. You can be a developer working with any programming language, working on any operating system and develop any kind of software."
"When we started VS Code, we took this approach where we wanted to really lead where there is the most demand. We have really tight integration of VS Code and TypeScript. VS Code is built on TypeScript. But we invested in a huge amount of language extensions," said Liuson.
"We have almost two million Python developers using VS Code and well over a million C++ developers using VS Code. And even our Java usage is approaching one million."
Microsoft didn't make up the term inner source and the approach means taking open-source development practices and applying them inside a single organization. GitHub and GitHub's Enterprise Server fits snuggly with this approach to help organizations collaborate but do so in private.
"Inner source means if you have private IP, but you're inviting other teams within the company to collaborate with you. That's the fundamental difference between open source and inner source. Today, it's very common in large enterprise – there are too many silos – but in the microservice architecture sometimes you have to debug an issue," Liuson said. "That's when you're thinking about using the open-source model within the enterprise context, with the right permissions. To me, it's not that different to how people collaborate on SharePoint, Word documents or G Suite."