Re:Everyday hassles in Go
by kasey_junk on Tuesday December 30, 2014 @08:52AM
(#8814562)
I think there is a third option that you are ignoring. Pike, Thompson & Co. are designing for a different problem set than the blog authors.
Golang seems to shine at very simple, concurrent tasks that can be passed from one set of developers to another regardless of sophistication levels of those teams. It seems to fail pretty miserably at making a single sophisticated developer vastly more productive. It's what Java would have been if they'd thrown away the write once/run anywhere goal and never gone down the J2EE box canyon.
There is nothing wrong with either goal btw, they just are in some ways opposites.
Golang seems to shine at very simple, concurrent tasks that can be passed from one set of developers to another regardless of sophistication levels of those teams. It seems to fail pretty miserably at making a single sophisticated developer vastly more productive. It's what Java would have been if they'd thrown away the write once/run anywhere goal and never gone down the J2EE box canyon.
There is nothing wrong with either goal btw, they just are in some ways opposites.