Linked by Thom Holwerda on Mon 11th Feb 2013 22:59 UTC
Thread beginning with comment 552227
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: My thoughts on Go
by satsujinka on Tue 12th Feb 2013 18:15
in reply to "RE[2]: My thoughts on Go"
RE[4]: My thoughts on Go
by lucas_maximus on Tue 12th Feb 2013 18:22
in reply to "RE[3]: My thoughts on Go"
RE[4]: My thoughts on Go
by Nelson on Tue 12th Feb 2013 18:57
in reply to "RE[3]: My thoughts on Go"
Don't get me wrong, I love Go and I think it does stand on its own, and while it has weaknesses, it also has clear advantages, in a neat simple little package.
Go is simple. The compilers are simple to deploy and cross compiler. The inheritance story is dead simple. They seem to be carefully planning out design before throwing in features willy nilly (Generics, Exceptions, etc.) .
I just think it'd be augmented by an IDE. Without one its still perfectly usable, these are just nit picks.





Member since:
2005-11-29
The language doesn't inherently afford you a lot of the expressiveness of other OO languages in their object model. You can't for example, at a glance, tell which interfaces a given "object" (as loose as the term is used in Go) implements.
That's where I think an IDE and the language can split the difference and make up for that. There are other small instances too like the fact that IDEs can help remove the stigma surrounding some of the more exotic syntax choices. That's valuable too.
it is my belief that a programming language is nothing without the tooling, a complete stack from beginning to end.