When was the last time you wrote a micro service that compiled to a single binary and interop'd seamlessly using grpc in C#? I'm going to guess the answer is n

When was the last time you wrote a micro service that compiled to a single binary and interop'd seamlessly using grpc in C#? I'm going to guess the answer is never, because it's basically impossible to do. Do you care? I doubt it, but some people really do. It's just different use cases for different things. Sure, go has its problems, but needing a large heavy IDE isn't one of them. That's really important to some people. /shrug > Oh, and when I have to use Go, I find a chore to write generic code... Oh man, don't even start. If you don't like go, don't use it. It was just one example of tooling that's better than C#. Rust, node, clojure, heck, even python has a better story for 'pick up and start using' than C# does at the moment. Do we really need to start digging down into how fundamentally terrible nuget is as a package manager, and how I personally find it like installing Master of Magic using 3 1/4 inch disks one by one when it screws up, or the feed screws up (like it did TODAY for about 4 hours)? nah. No one cares. Let's just leave it at: There are some valid concerns people have with the C# ecosystem, and using C# on non-windows platforms. It's a work in progress. At least we now have a coherent direction for everything going forward~