@pancakes kind of self-inflicting damage on MS part because that means people start using the mono debugger, being less dependent on their software, so they lose control of the narrative.
@LiquidParasyte yes. VSCode is kind of like Chrome (I'm not talking about electron). It's Microsoft's branded distribution of Code - OSS, which is like Chromium for this analogy. vsdbg only works on VSCode, it doesn't even work on the core project Code - OSS, let alone forks like VSCodium
@griibor there's free-csharp-vscode aka C# from Open VSIX Registry. you need to manually install the extension file or switch your VSCode to Open VSIX. switching may make other extensions unavailable
@kura@Jain oh thank you! i'm using "Code - OSS" on Linux. because it isn't "Visual Studio Code", the "Code - OSS" distribution published by Microsoft vsdbg doesn't work. i'll give this a go though
@kura@Jain i know i'm just frustrated that that's the state of the ecosystem. everything is "free, open-source, cross-platform" except for the debugger
@kura@pancakes i have to test it somewhen... without proper language server support & debugging tools it is not a sustainable open source way and im glad you told me that there is such thing now
@pancakes vscode has always been an "open core" product, but the open part has been shrinking for years. The recommended plug-in for Python is restricted to the proprietary build too.
Guess "shrinking open core" is the evolution of EEE. As users, we should prefer copylefted software.
1
1
1
1❤3⭐2🪛1
