> And Go is a great language when efficiency is not quite as important as productivity.
The Go problem is not so much that it's inefficient, it's that the lack of compile-time checks encourages bug-prone cowboy coding which is often mistaken as "higher productivity". Because no one's measuring the very real productivity impact of easily preventable software defects.
The Go problem is not so much that it's inefficient, it's that the lack of compile-time checks encourages bug-prone cowboy coding which is often mistaken as "higher productivity". Because no one's measuring the very real productivity impact of easily preventable software defects.