vscode-csharp

The tooling is not entirely open or freely available. If you, for e.g., want to debug you have to use MS tooling.[0] You also can't use VSCodium because only the MS built/distributed version of VSCode contains the proprietary binary blobs necessary to debug C# (which also means you're forced into the aggressive telemetry and other data collection built into the non-open source distribution of VSCode). They've also taken steps to lock down the LSP support for C#, which once again requires that you use a MS sanctioned editor to write C#. [1] I really enjoy writing C# and think dotnet is a great platform to develop for, but the barriers preventing me from building more projects on it is that I don't want to be forced to use VSCode or Visual Studio. I also don't want to get too invested into a particular piece of tooling that is going to be r

Unfortunately, the link does not point to where I intended as it got rid of the #part, here is the target --> https://github.com/dotnet/vscode-csharp/issues/5276#issuecom...

> They did a wonderful job with C# and .NET Core. And VSCode. One thing all three have in common is that they are all FREE to use--they don't make Microsoft any money directly. And, for the segment of the developer tools market that wrangles C# code, if VSCode gets too good, it becomes a threat to a cash cow: Visual Studio. Start here: https://github.com/OmniSharp/omnisharp-vscode/issues/5276#is...

Yeah but it's made by Microsoft. I knew they were going to kill Atom the day of the Github acquisition. Right now vscode is good, but I have no guarantees that in 5 years they won't pull an asshole move and I'll have to go through all of this again. In fact, depending on who you ask, it's already happening with the C# extension[1], and nothing promises me that the same won't happen with other parts of the editor. [1] https://github.com/omnisharp/omnisharp-vscode/issues/5276