Agreed, but the language is sufficiently (edit) MORE verbose than Python that it is still a valid strategy to write in Python first, and then rewrite in Go for performance..
Wow. Great to hear. My current big project is all in Python. Maybe a rewrite is in my future if I find the project successful.
It translates fairly directly as well, even with the differences in OO and multi-processing/threading.
If go is less verbose, then why write it in a more verbose language first? The reality is, go and python are pretty much even for verbosity, and there is absolutely no benefit to writing your app in python first and then go. You'd be better off writing it in go and then rewriting it in go if you want the benefits of learning from your first attempt.
I'm a fan of Go, but Go is definitely a bit more verbose than Python.
I mean't more verbose, sorry.
I'm thinking the same.
This summer vacation is reserved for Go :)