See https://isdotnetopen.com/ for a concise summary of open problems in the .NET ecosystem and a detailed account how the .NET platform is becoming closed to ensure it is only useful if you are a customer who pays for Visual Studio.
Microsoft discloses plans to turn parts of VS Code C# extension to closed source
11–20 of 42 posts
Re: Microsoft discloses plans to turn parts of VS Code C# extension to closed source
#12So, 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.
ecosystem defaults was: open, like ruby, golang or rust
ecosystem defaults now: closed, proprietary to ensure the programming language is only useful if you are a paying customer of Visual Studio.
See the problem? More at https://isdotnetopen.com/
Re: Microsoft discloses plans to turn parts of VS Code C# extension to closed source
#13Microsoft being their usual selves?
please continue to use and promote C# and .net, we definitely won't be doing the same for those the moment we get the opportunity
Re: Microsoft discloses plans to turn parts of VS Code C# extension to closed source
#14Earlier quoted context omitted.
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.
How is that bad faith? Isn’t that, for example, exactly what Gitlab does?
It would be bad faith if they removed access to the open source code somehow.
Re: Microsoft discloses plans to turn parts of VS Code C# extension to closed source
#15> integrates both open-source components, like Roslyn and Razor, with closed-source components
This kind of thing is why copyleft is so important. Microsoft wouldn't be allowed to do this if the tools in question were GPL'd (and external contributors didn't have to forfeit their copyrights with a CLA).
Re: Microsoft discloses plans to turn parts of VS Code C# extension to closed source
#16> integrates both open-source components, like Roslyn and Razor, with closed-source components This kind of thing is why copyleft is so important. Microsoft wouldn't be allowed to do this if the tools in question were GPL'd (and external contributors didn't have to forfeit their copyrights with a CLA).
They are the primary contributor to both things.
It’s quite amazing that most people just associate open source with “free” not realizing that time is literally money.
Re: Microsoft discloses plans to turn parts of VS Code C# extension to closed source
#17> integrates both open-source components, like Roslyn and Razor, with closed-source components This kind of thing is why copyleft is so important. Microsoft wouldn't be allowed to do this if the tools in question were GPL'd (and external contributors didn't have to forfeit their copyrights with a CLA).
They are the primary contributor to both things. It’s quite amazing that most people just associate open source with “free” not realizing that time is literally money.
But they're not the only contributor, so they'd have to either get permission from everyone else or revert all their changes, which would have been a nontrivial effort.
Re: Microsoft discloses plans to turn parts of VS Code C# extension to closed source
#18Earlier quoted context omitted.
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.
How is that bad faith? Isn’t that, for example, exactly what Gitlab does? It would be bad faith if they removed access to the open source code somehow.
It's advertised as open source, but the published source code isn't what people actually run (when using their official binaries).
Re: Microsoft discloses plans to turn parts of VS Code C# extension to closed source
#19Shitty Microsoft
Re: Microsoft discloses plans to turn parts of VS Code C# extension to closed source
#20thankfully vscode is still OSS, I am an emacs user myself but sometime i like to go see features and ideas from vscode and see how to implement it in elisp