A Farewell to Go
churchwood.at
A Farewell to Go
1–10 of 85 posts
Re: A Farewell to Go
#2Haven't used Go in about a year and change, is Google going to pull an Angular and pull the rug out from under developers for Go 2.0?
Re: A Farewell to Go
#3I disagree with the authors feelings on code formatting. Gofmt is one of the best features of Go, especially when reading others code.
Re: A Farewell to Go
#4 Interfaces help to solve the problem with methods of objects, but not with data members.
Re: A Farewell to Go
#5Haven't used Go in about a year and change, is Google going to pull an Angular and pull the rug out from under developers for Go 2.0?
going to? Hard to say, doesn't sound like it at all though. They want a non-breaking release, to prevent the Python 2-3 debacle. However, what will happen only time can tell.
Re: A Farewell to Go
#6I also disagree on the code formatting front – once you get used to it, gofmt really is the best thing ever.
However, all the rest of the points are pretty valid. Go has the potential to be an awesome language and environment, and minimalism as a language attribute is attractive. But it's so frigging annoying to use in practice.
Re: A Farewell to Go
#7[deleted]
Re: A Farewell to Go
#8Haven't used Go in about a year and change, is Google going to pull an Angular and pull the rug out from under developers for Go 2.0?
Go 2 considered harmful?
Re: A Farewell to Go
#9http://www.golang.sucks/ is both a better and a more comprehensive critique of Go.
Rob Pike's quote about "They’re not capable of understanding a brilliant language" is extremely unfortunate, and a missed opportunity to elevate the art/science of programming and the much larger understanding of information theory in general for all programmers, instead of trying to appeal to the lowest common denominator. My first question would be "why would anyone pick a language that is designed out of the box to ultimately limit the depth of their understanding?
Re: A Farewell to Go
#10This was a terribly worded blog post.
The problems the author faced with go were so paper thin -- I don't think they warranted claiming "every line of go i've written is now deprecated".
It's pretty clear going into go from the initial HelloWorld -- that you are expected to:
1 - use gofmt 2 - won't have inheritance 3 - Drudge your way through a solution for dependency versioning
To complain about it so late into a project really speaks poorly to the author.