VS Code is open source, but its essence is exclusive?

Over the years, Microsoft has made great efforts to open source, which I am very shocked and happy about. I understand the skeptics. I saw everything in the community when Microsoft was not friendly with Linux at first, but I think only time can prove everything. I feel that Microsoft’s contribution far exceeds that of the people who spend their days attacking various Linux distributions. Therefore, I very much agree with the efforts made by Microsoft, especially the visual studio code is excellent. < / P > < p > when I tweeted on this topic, I was advised to use vim. Thank you for your reply. I will and am using VIM, of course, but that’s not the point. Visual studio code is a very popular editor and is often recommended to novice developers. The main reason why I use Visual Studio code is that it has excellent real-time sharing function, which is the perfect solution for remote pairing programming. I have been using Visual Studio code for a while, successfully implementing remote mentoring and working with other developers at all levels of experience. Most programmers can normally use “normal” editors such as vs code, and whether to use Emacs or VIM depends more on their accumulated experience. < / P > < p > in addition, I also like the various remote extensions of vs code, which can help us develop in remote servers or local containers. < / P > < p > I once read a license that said real-time sharing can only be used with the visual studio family of products. That sounds strange. Vs code is open source, isn’t it? < / P > < p > of course. Vs code is fully MIT licensed. The binary distribution of vscode is licensed separately to support telemetry and protect Microsoft’s trademarks and products. It’s not particularly surprising. Although I don’t like telemetry, some people don’t care. But these extensions do make vs code more attractive. For me, it’s because these extensions are better than the lightweight sublime for vs code. < / P > < p > however, these extensions are licensed, limiting their use and their online service parts only with the visual studio family of products. Read the license for real-time sharing and remote extension. < / P > < p > for me, real-time sharing is the most important function. Like Google documents, it implements collaborative code editing, terminal sharing, port sharing and many other functions. I know atom has this extension, but I haven’t looked at the license and haven’t tried it. < / P > < p > remote is also a very powerful extension for people who need to work on servers or containers via SSH. We only need to install the extension on the target machine to implement the language server. I know that sometimes it can have a terrible impact on the server, but this extension is very practical and works normally. < / P > < p > if some very attractive features can only be used in the visual studio product family, then I don’t quite understand the significance of vs Code as an “open source” project. I began to doubt that the so-called “expansion” is likely to be a link in the series of acceptance expansion elimination. In addition, I was very disappointed because it made it impossible for people to build compatible plug-ins for VIM or any other editor. If we can use this extension in all IntelliJ, we believe it will be more powerful. < / P > < p > although there is a code base for sharing extensions in real time on GitHub, there is only documentation and problem tracking, and there is no code. The same is true for remote extensions. < / P > < p > in addition, using vs code to expand the market also requires a proprietary license, which is undoubtedly adding to the problem. All of these open-source developers have to cede their extensions to one of the world’s largest technology companies. And these extensions cannot be used for other purposes on the market. Even if the nature of open source software, such as open source and open source software, is lost. < / P > < p > What does this mean in practice? I think it can prevent competition. For example, the vs Codium project provides vs Code binaries that do not include proprietary parts. What’s more, vs Codium has not expanded the market due to the exclusive licensing of the market. There is another open source alternative called open VSX, but because it is not standardized, it lacks many extensions, and still does not allow the use of real-time sharing and remote. < / P > < p > this also makes code server unavailable to expand the market, otherwise it will be very suitable for me to develop on iPad pro. I can still use the editor, but many packages are not included in openvsx. < / P > < p > real time sharing and remote as a powerful extension, are bound with visual studio code for sales. In the market, vs code is open source. It’s easy to use the editor and install extensions, giving the impression that you are using an open source software suite, and Microsoft is only responsible for hosting services that identify and connect you and your partners. < / P > < p > however, it’s not just these services that don’t have open source. As far as I know, these extensions are not open source projects, require separate licenses during distribution, and are not allowed to be used with any product except visual studio. < / P > < p > I don’t feel like it. At first, I was not interested in electron based editors, and vs code was lighter than atom, so I accepted vs code. < / P > < p > partially agreed. I’m also dissatisfied that some of the widely used extensions are proprietary. But if these extensions require Microsoft servers, they certainly have a good reason. Even if they don’t have a good reason, it’s okay for a company to keep a product that they think is strategic. After all, they have no obligation to let go completely. < / P > < p > if we want to discuss whether vscode itself belongs to open source, we need to base on the published code. In addition, we need to consider the personnel invested by Microsoft in maintaining the open source link of the product. < / P > < p > dissatisfied that some extensions are closed source, and also complained that this approach seems a bit inappropriate, especially if we can develop an open source extension with the same function. < / P > < p > this also means that if others want to create their own proprietary extensions, it’s no problem. At the same time, the basic functions of vs Code remain unchanged. < / P > < p > today, we can really say that real-time sharing and remoting are the best extensions, and because the authors of these extensions decide not to share code, they are proprietary. But this time the author is Microsoft itself. < / P > < p > however, since the extension itself is not an integral part of vs Code itself, anyone can create an open source extension with the same functionality. < / P > < p > however, what I disagree with is that if you want to use vs Codium to build your own editor, you still can’t use services for the vscode expansion market. Even if those extensions work, even if the extensions themselves are open source. Therefore, even if vs code has a lot of open source code extensions, it doesn’t mean it can be reused, because the extension service will limit you. < / P > < p > of course, you can also publish the extension to other public services, but this service does not exist at present, and it needs to be re released after all. < p > < p > technology giants will use their profits from one dominant field to compete with another. Building a very large cloud costs billions of dollars. Amazon uses its e-commerce business to subsidize AWS, Google has advertising services, and Microsoft has services such as windows and office. < / P > < p > Microsoft has a long history of offering some products to attack competitors. Netscape is the best example. Microsoft is very good at being a developer’s tool. How can business editors compete with vs code, which Microsoft has invested a lot of resources and provides for free? < / P > < p > Microsoft hopes to support Linux based container development on windows through their remote editing tools. It is then used to debug containers running in the cloud through vs code. But they prohibit competitors from using server-side extensions. So we need an open source server. Continue ReadingDeveloped a “plug and play” solar power generation scheme, and “5B” won a $12 million round a financing

Author: zmhuaxia