2 ms·

> A startup is about getting a product out to market as soon as possible, and hopefully as cheaply as possible, which can best be done with open and freely avai

> A startup is about getting a product out to market as soon as possible, and hopefully as cheaply as possible, which can best be done with open and freely available tools. C# tooling is open and freely available. The source for the compiler and tools are all on github and the tools are all available free to download and use.

conor- 3y ago
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 rug pulled down the road by some MS product manager who isn't aligned with the "MS <3 OSS" side of the company. [0] https://github.com/dotnet/core/issues/505 https://github.com/dotnet/core/issues/505 [1] https://github.com/dotnet/vscode-csharp/issues/5276 https://github.com/dotnet/vscode-csharp/issues/5276
- naasking 3y ago
  Those links both show the tooling is freely available, and for the core debugging interface, there are open source implementations as documented at those links as well. I'm not sure what the problem is.
  - aragilar 3y ago
    There's a number of caveats on that statement though (e.g. "freely available" only to vscode users), and that is the problem.

conor- 3y ago

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 rug pulled down the road by some MS product manager who isn't aligned with the "MS <3 OSS" side of the company. [0] https://github.com/dotnet/core/issues/505 https://github.com/dotnet/core/issues/505 [1] https://github.com/dotnet/vscode-csharp/issues/5276 https://github.com/dotnet/vscode-csharp/issues/5276

naasking 3y ago
Those links both show the tooling is freely available, and for the core debugging interface, there are open source implementations as documented at those links as well. I'm not sure what the problem is.
- aragilar 3y ago
  There's a number of caveats on that statement though (e.g. "freely available" only to vscode users), and that is the problem.