For the thousands of devs shipping non-trivial code, keep going!
For the thousands of devs shipping non-trivial code, keep going!
https://cloud.redhat.com/blog/kubernetes-deep-dive-code-gene...
Both of these projects have had to go way out of their way to make things work without generics, but they are large enough projects and have enough resources that they can do this. Both are actually really great examples of why Go is a bad choice until generics are added and have first-class support. Even C would be preferable over something where there are no generics.
I've been writing Golang for 5 years and have never had need for generics.
It's nothing to with resources, it's just understanding how to build software.
Your retreat to C is a bit sad - I'd be happy to help you if you've got any Go you're struggling with?