Re:OpenVSX, which VSCode forks rely on for extensions, down ...
by int_19h on Friday April 25, 2025 @04:29AM
(#43791467)
It's even worse. VSCode used to be more open source originally, back when it was enthusiastically adopted. And then, gradually, official extensions started replacing parts with closed blobs with onerous licensing terms. C# and Python extensions have both suffered from this. Although the C++ one was never fully open, if I remember correctly.
[ Parent
| on HN ]
Re:OpenVSX, which VSCode forks rely on for extensions, down ...
by wilsonnb3 on Friday April 25, 2025 @01:24PM
(#43796275)
Same for the c# one I think, the old language server was and is still open source but the .net core debugger has always been proprietary.
I imagine it is because it is derived from the Visual Studio debugger in some fashion. JetBrains ran into the same problem with Rider back in the .NET core days and had to write their own debugger.
Re:OpenVSX, which VSCode forks rely on for extensions, down ...
by neonsunset on Friday April 25, 2025 @04:14PM
(#43798082)
Roslyn language server is OSS too: https://github.com/dotnet/roslyn/tree/main/src/LanguageServe...
There was never an issue with Omnisharp OSS-ness itself nor what replaced it. It was always about debugger and then "Dev Kit" extension which builds on top of the base one - "Dev Kit" is what isn't OSS and what requires an account.
There is also an alternate open debugger: https://github.com/Samsung/netcoredbg / https://github.com/muhammadsammy/free-vscode-csharp (extension fork which swaps vsdbg out for this one)