> Sorry, what? I fail to understand your question, but can reiterate. The available good debuggers are proprietary, including the one that only runs in the pro

> Sorry, what? I fail to understand your question, but can reiterate. The available good debuggers are proprietary, including the one that only runs in the proprietary version of VSCode. Thus you can’t really use it in another IDE - Same shit as with the original Visual Studio. OmniSharp is an effort to replace the proprietary debugger, but lacks features in comparison. > ... what is "Visual Studio baggage"??? Patterns and actions relying on features in Visual Studio, either softly because every guide uses them (modifying project properties, changing the startup project, installing a package) and hardly because the implementation is literally inside of Visual Studio (almost hot reload). > If anything, .NET had a Visual Studio lock-in back in those days, but not today ... And it wasn’t great. Having had a .NET Framework job for a while I learned to like C# and hate Visual Studio. I’m glad most tutorials now use VSCode on Macs to get as far away as possible from VS and MS-isms. I’m not glad they’re attempting to bring that terrible Visual Studio and Windows entanglement back. Hence I agree with the forker. > Also are we talking about .NET or "programming languages" here? Or both? They’re so closely related it doesn’t make that much sense to discuss them separately in this case. If you want to use C#, you need .NET. Technically this is about .NET, but probably with the main intention to save C#.