Oh, and when I have to use Go, I find a chore to write generic code as if I was back in 1992 using Borland C++ 2.0 for MS-DOS, with pre-processor based code generation for BIDS or still using Java 1.4 (EOL in 2008).
Oh, and when I have to use Go, I find a chore to write generic code as if I was back in 1992 using Borland C++ 2.0 for MS-DOS, with pre-processor based code generation for BIDS or still using Java 1.4 (EOL in 2008).
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~
You mean by using something like Mono -aot, CoreRT, IL2CPP?
> Do we really need to start digging down into how fundamentally terrible nuget is as a package manager,
No, because in spite its issues, it still runs circles around the half-baked solutions that Go devs are still trying to fix.
Nuget is such a pile of rubbish it's not even worth arguing about; if that's the best package manager you've ever used, you should really go check https://github.com/fsprojects/Paket out.
(they also helpfully articulate why nuget isn't really very good)
The irony is that the folk from go-world have finally acknowledged the package management solution they have is really terrible, and they're building a lovely new one (https://github.com/golang/dep).
Maybe sometime in the future you'll be eating your words, when go has a lovely package manager.
...and c# still has nuget.
:)