Linked by Thom Holwerda on Wed 11th Nov 2009 14:21 UTC
Permalink for comment 394016
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
More Features »
Sponsored Links



Member since:
2009-06-30
All issues (?) you've pointed out are just your personal preferences regarding the syntax. Is it really that important whether the import statement uses parentheses or not? To me any reasonably readable, regular and compact syntax will do, as long as the language has semantics and libraries I need.
The language is OO (more than C++ or Java for that matter), has very flexible type system and built-in concurrency primitives. Feature set is pretty conservative but it feels right for system-level programming.
Whether it is enough - hard to say. To promote a new system level language Google needs more than just a compiler, debugger and a basic class library. For start they should make Go a core part of their frameworks, just like what Sun or Microsoft did with Java or .Net.
I'm also a bit concerned about the binary compatibility, this issue should be dealt with asap or Go may end up going C++ route, where each compiler/architecture uses different calling conventions, symbol names mangling etc.