 |
||
 |
 |
 |
 |
 |
|
| I'm really enjoying Go by Entropy Stew 09/01/2013, 7:52am PDT | ||||
 |
 |
|||
| Not only is it nice, it's profoundly useful almost immediately, so my enjoyment is actually translating to me writing some of it at work, which is unusual. I love channels - they're like a radically better implementation of the first big multithreaded java architecture I wrote to deal with the c10k problem. The strong type system is more useful than onerous, especially after having written so much Perl. The standard libs are really, really useful (especially the http daemon). Like, you can convert a struct to or from JSON via runtime reflection (via a library that does it for you), or you can attach metadata to the struct member definitions to specify the exact mapping yourself. I'm dangerously close to becoming a fanboy.
Another interesting aspect of the language is how easily it is to integrate with C libraries. You can call C functions easily, and C structs get mapped into corresponding Go types. This only works to a point, as not everything C has an equivalent in Go. Anything Go doesn't understand, like unions inside a struct, just get mapped as a byte array (irritating to deal with in Go due to its strong typing). Callbacks are also a pain in the ass, inviting you to write a C shim. I learned this in my failed first attempt at writing a couchbase smart client based off libcouchbase. Painful as the experience was, it was further than I would have gotten trying to do the same in Perl, and I intend to take another shot at it. The main problems with it are a lack of generics, no version info in the package requirments, the crude GC, and the crude goroutine scheduler, none of which are bad enough to make me stop using the language. -/ES/- |
||||
 |
 |
|||
|
