> Because they're Go experts, they know the cost of using Go upfront, and they're equipped to make the decision whether or not it's worth it
Well maybe not.
If I’m an expert in only Java 6, I might not be aware of all sorts of useful features that other languages have, such as sum types, traits, type inference… I only know one side of the trade off.
I might be vaguely aware of those ideas and dismiss them because I can’t imagine how they would fit in my Java 6 workflow.
And yet when some of them arrive in later Javas, I begrudgingly use them. Years later I can’t imagine how I ever lived without them!
We’ve seen this play out so many times.
Remember when lambdas were just for weird functional languages?
Well maybe not.
If I’m an expert in only Java 6, I might not be aware of all sorts of useful features that other languages have, such as sum types, traits, type inference… I only know one side of the trade off.
I might be vaguely aware of those ideas and dismiss them because I can’t imagine how they would fit in my Java 6 workflow.
And yet when some of them arrive in later Javas, I begrudgingly use them. Years later I can’t imagine how I ever lived without them!
We’ve seen this play out so many times.
Remember when lambdas were just for weird functional languages?