Go has a shorter time, and that’s the measuring stick in this area.
It's often about how fast one can deliver maintainable software that works well enough.
Go was so "easy" that I was immediately productive, but this resulted in often suboptimal and messy code that I had to refactor over and over again due to concurrency, abstraction, or performance issues.
True productivity is hard to measure.
Pretty sure that Go isn't equally restrictive (while still being garbage collected).
It is a better option than keeping using C, and it would have been great in 1996, but that is about it.