News for hackers. Stuff that matters.
Re:Why I went from Python to Go (and not node.js) by ak217 on Friday September 14, 2012 @04:54PM (#4523903)
Idiomatic Go: http://golang.org/doc/effective_go.html

Idiomatic Python: http://python.net/~goodger/projects/pycon/2007/idiomatic/han... (doesn't cover a number of important things)

When comparing the two, I'm not impressed with Go.

Re:Why I went from Python to Go (and not node.js) by winter_blue on Friday September 14, 2012 @05:25PM (#4524053)
The first link, Effective Go doesn't talk about the philosophy behind idiomatic Go, like _Code like a Pythonista_ does. There is however snippets of Go code on that page, and it's fairly reminiscent of C/C++. I don't really see that as a drawback, for I believe C code is fairly readable for what it offers (speed.) Go likeness to C doesn't offend me one bit, considering the power and speed it offers versus C.
Re:Why I went from Python to Go (and not node.js) by lambda on Saturday September 15, 2012 @12:12AM (#4525271)
What makes you unimpressed? Why do you think that Python clearly wins? Do you think that the additional type safety, namespace safety, and ease of concurrency in Go are worth nothing? Or do you just think that Python has more that outweigh that?

I know that I frequently kick myself in Python when I typo a name somewhere, and everything dies far beyond where I made the mistake because it goes along happily storing something into that typoed variable, and then when I read it later it has the wrong value, and it takes me a while to trace back and find where I made the typo.

Re:Why I went from Python to Go (and not node.js) by paul-woolcock on Saturday September 15, 2012 @11:05AM (#4526220)
This is what linting tools like pyflakes are for. Running it as a prerequisite to running the test suite means that I don't have to run all my tests just to find out that I misspelled a variable name.