Impressions of Go

Re:Impressions of Go by jbooth on Tuesday July 23, 2013 @12:50PM (#6091219)

'go test' is pretty straightforward. Not so much a framework as a tool -- I think you'll find that most of the language carries the opinion 'Frameworks are a straightjacket, libraries are a tool'.

[ Parent | on HN ]

Re:Impressions of Go by mitchty on Tuesday July 23, 2013 @01:44PM (#6091632)

Gotcha, i've only bought the pragmatic programmers ebook so far. Past that i've really not done much.

I take it the go vein is more akin to: everything a framework(insert noun here) does for you it does to you?

I wholeheartedly agree, note i've used ruby for about 10 years aka: before rails, and there are times I want to strangle rails with a garrote for some of its choices in how it does things.

Ranting done, do you/anyone have any specific codebases I should look to for a good example of go programming methodology?

The scripts that will be replaced tend to be fairly heave with i/o and other stupid process manipulation, i.e. detect that some subprocess sigtermed etc... pretty boring stuff normally but I use threading rather heavily in ruby at the moment. So doing concurrency a bit more easily would be nice, especially since most of the things are just i/o derivatives of pack/unpack calls on things across many many devices. I've tested out celluloid with ruby and its great, but again that gets to gem/dependency management horror.

Guessing I just need to work with it and I'll find things out. Should hop into a go irc channel if there is one on freenode.

[ Parent | on HN ]

Re:Impressions of Go by jbooth on Tuesday July 23, 2013 @02:10PM (#6091825)

#golang-nuts on freenode. The effective go document is pretty good for basics, especially concurrency.

[ Parent | on HN ]