2 ms·
Let's imagine that a few years from now, MS starts advertising Azure right inside VSCode, and they start releasing features which favor Azure integration, and a
by skohan 6y ago
Let's imagine that a few years from now, MS starts advertising Azure right inside VSCode, and they start releasing features which favor Azure integration, and actually cause problems when working with GCP.
Now imagine I as a developer want to pick up shop and move to another editor, but it turns out my workflow depends on proprietary extensions which are only available on VSCode, and my velocity will be cut by 70% if I switch editors.
If MS owns the interface most developers have to their code, there are all kinds of ways they could leverage that to your disadvantage.
- ta8594505930 6y agoIn this scenario would you be relying on a proprietary extension to interact with GCP developed by Microsoft? Surely you would want to use a Google or Third-party developed extension to do that right? And in that case the developer of that extension would have a vested interest in making it available to you again, potentially in a forked version of VS Code. As long as the editor is open source extension developers can just fork it and create a new public directory of extensions. The only thing you potentially lose is Microsoft's proprietary extensions which are likely to always work well with Microsoft products and you really shouldn't use them to interact with Microsoft's competitors.