I know how to write golang, which is why I'm well aware of its shortcomings and the issues its inferior design causes, and the costly bandaids that have to be implemented to poorly attempt to mitigate said issues.
It's a huge code base, with literally thousands of sub-projects, with non-overlapping teams working on them. When I see the same issues arise, the only common thing is the language.
Comments
I know how to write golang, which is why I'm well aware of its shortcomings and the issues its inferior design causes, and the costly bandaids that have to be implemented to poorly attempt to mitigate said issues.
Got an example repo you've worked on as happy to help work with the ecosystem rather than against it?
It's a non-public code base.
So a single project, that you designed and built is causing you problems?
I don't think Go is the problem
It's a huge code base, with literally thousands of sub-projects, with non-overlapping teams working on them. When I see the same issues arise, the only common thing is the language.