It's not a one time cost though. Whenever you have options you will have projects jumping and forth between different build tools.
This was a frequent occurence on the JVM platform as libraries moved from Ant to Maven to Gradle over the years.
The core of my work is on the operations side rather than on development (although I do a good bit of that as well), so my perspective is that this initial overhead is a one-time cost for using a library, and that I can live with that.
> I think it's time go devs acknowledge the fact that there is an serious issue here, instead of resorting to the ususal "you don't need that in go".
Encountering this and a lot of "well this is the way Google does is so we should too" was a big part of what inspired this post.