3 ms·
I don't think the author meant this to be extrapolated as a critique of the stewardship of Go's developers ("You guys haven't caught up to Java yet!"). I read i
by weberc2 9y ago
I don't think the author meant this to be extrapolated as a critique of the stewardship of Go's developers ("You guys haven't caught up to Java yet!"). I read it as "Go isn't optimizing this case today, and Java shows us that it's at least possible".
- Someone 9y agoI read the title as indicating that he did mean it (somewhat) as a critique. It would have been kinder to say "Go does not inline functions when it COULD" instead. On the other hand, I'm not 100% convinced that it could without giving up fast compilation speed, a feature that the language's designers deem very important.
- weberc2 9y agoFair point. "Should" is pretty opinionated, even if I'm inclined to agree with the opinion.