Microsoft discloses plans to turn parts of VS Code C# extension to closed source
1–10 of 42 posts
Re: Microsoft discloses plans to turn parts of VS Code C# extension to closed source
#2So, is this the Extend part now? Embrace is over? (I don't understand each of the terms of the slogan enough)
Side note, I am guessing this means that Vim, Emacs etc using LSP don't get C# intellisense anymore?
Re: Microsoft discloses plans to turn parts of VS Code C# extension to closed source
#3>> "We plan to create a new “LSP Tools Host” component (not an official name ), which integrates both open-source components, like Roslyn and Razor, with closed-source components, offering a wider array of tooling capabilities."
>> "Once the “LSP Tools Host” is complete, this will become the default experience for the C# for VS Code extension. Existing users will be able to choose between the open-source OmniSharp powered system that exists today, or the new “'LSP Tools Host” which will provide access to additional experiences. The “LSP Tools Host” will not be open-sourced, but we plan to communicate with the community along the way to help guide our future plans."
'Microsoft <3 Open Source' unless it threatens a business unit.
Re: Microsoft discloses plans to turn parts of VS Code C# extension to closed source
#4>> "We plan to create a new “LSP Tools Host” component (not an official name ), which integrates both open-source components, like Roslyn and Razor, with closed-source components, offering a wider array of tooling capabilities." >> "Once the “LSP Tools Host” is complete, this will become the default experience for the C# for VS Code extension. Existing users will be able to choose between the open-source OmniSharp po…
They did the same thing with closed source Pylance, which is built on top of the open source Pyright. Pretty despicable behavior no matter how you cut it.
Re: Microsoft discloses plans to turn parts of VS Code C# extension to closed source
#5So, is this the Extend part now? Embrace is over? (I don't understand each of the terms of the slogan enough) Side note, I am guessing this means that Vim, Emacs etc using LSP don't get C# intellisense anymore?
the 90s saying was Embrace,Extend,Extinguish.
pick an internet or engineering standard: implement the standard in a correct, technical way (Embrace); add MSFT proprietary extensions using an IDE, a method of notification, graphical desktop software with convenience functions, etc (Extend); now, require MSFT software to use that result, use finance to market it, use contracts to require company-wide use of standard MSFT computers -- sales for vendors that are not MSFT will fall on the open market because enough companies have already purchased the MSFT windows desktop, either required by the company/department or when purchasing the PC -- why spend more money when you have what you were after, and it is built in? In Redmond, winning more sales is not enough -- kill competing companies and/or write extensions to the standard-at-hand that require MSFT products (Extinguish).
Recall that the Windows license was sold without consent of an individual user, it was included when the PC was purchased, through a legally enforced agreement with the PC manufacturer. These methods made Bill Gates the wealthiest man in the World for twenty sequential years or so, with multiple anti-trust convictions and a row of books published on the details.
Re: Microsoft discloses plans to turn parts of VS Code C# extension to closed source
#6>> "We plan to create a new “LSP Tools Host” component (not an official name ), which integrates both open-source components, like Roslyn and Razor, with closed-source components, offering a wider array of tooling capabilities." >> "Once the “LSP Tools Host” is complete, this will become the default experience for the C# for VS Code extension. Existing users will be able to choose between the open-source OmniSharp po…
They did the same thing with closed source Pylance, which is built on top of the open source Pyright. Pretty despicable behavior no matter how you cut it.
I'm by no means in favor of closed source extensions, but I feel it's worth mentioning that yes, Pyright is open source and Pylance isn't, but Pyright is also a Microsoft project. You can hardly make the argument that keeping all parts closed source would have been better.
Re: Microsoft discloses plans to turn parts of VS Code C# extension to closed source
#7So, is this the Extend part now? Embrace is over? (I don't understand each of the terms of the slogan enough) Side note, I am guessing this means that Vim, Emacs etc using LSP don't get C# intellisense anymore?
Presumably other editors won't get the new language server, unfortunately. However the ability to use the current open source language server (which is not made by Microsoft) should remain unaffected.
Re: Microsoft discloses plans to turn parts of VS Code C# extension to closed source
#8So, is this the Extend part now? Embrace is over? (I don't understand each of the terms of the slogan enough) Side note, I am guessing this means that Vim, Emacs etc using LSP don't get C# intellisense anymore?
Nothing that exists today is moving behind a closed-source model. Omnisharp will continue to be open and maintained but it won't be the default anymore.
Re: Microsoft discloses plans to turn parts of VS Code C# extension to closed source
#9EEE in 2022.
Re: Microsoft discloses plans to turn parts of VS Code C# extension to closed source
#10Earlier quoted context omitted.
They did the same thing with closed source Pylance, which is built on top of the open source Pyright. Pretty despicable behavior no matter how you cut it.
I'm by no means in favor of closed source extensions, but I feel it's worth mentioning that yes, Pyright is open source and Pylance isn't, but Pyright is also a Microsoft project. You can hardly make the argument that keeping all parts closed source would have been better.
I didn't mean to imply otherwise only that building prop. extensions on top of their own open extensions is nothing new for them and smacks of bad faith engagement.