You've misunderstood the debate. The concern isn't about Go turning into Boost; it's about Go becoming multiparadigm--about losing the property that "all Go code tends to be written in the same general way" and that people will invariably write code that optimizes for abstraction instead of readability and utility as invariably happens in other languages. If you're not used to Go, you'll probably write this off very quickly because you underestimate (as we all did before we tried Go) how nice it is to have standard, appropriately-abstract code. This is why the debate inside the Go community is more nuanced and amicable--people understand the tradeoff better; they're not shouting uninformed opinions nor pretending there is no tradeoff or that the tradeoff is "just FUD" based on their utter inexperience.