Linked by fran on Fri 22nd Jul 2011 21:02 UTC
Permalink for comment 482174
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 06/13/13 14:35 UTC
Linked by Thom Holwerda on 06/11/13 17:07 UTC
Linked by Thom Holwerda on 06/10/13 23:13 UTC
Linked by Thom Holwerda on 06/08/13 14:57 UTC
Linked by Thom Holwerda on 06/07/13 11:40 UTC
Linked by Thom Holwerda on 06/04/13 12:45 UTC
Linked by nfeske on 05/31/13 10:12 UTC
Linked by Thom Holwerda on 05/29/13 16:59 UTC
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
More Features »
Sponsored Links



Member since:
2006-03-17
... who has actually used Go - I can safely say it didn't matter what their problems with Java may have been, Go would have happened regardless of Java. Go is significantly different from Java, the "Defer/Panic/Recover" error handling, "gothreads".. it is a little odd - and can take some work to port other code to it, but worth looking at for most projects.
I had a fairly simple GTK#mono app I wanted to translate to Go, and it was significantly harder than I expected (mostly because of exception handling) but Go allowed me to efficiently multi-thread my app very easily. Its different and interesting - but be prepared to say goodbye to good 'ol "Try/Catch".
I would also say that Go needs better documentation, more like php.net and their contributed code samples.