golang

The goal is not to look like golang but to maintain locality: Implementation of one thing should be at one place, not at two different places.

Even things like asserts in python, (assert is even a builtin in python, no need to import unittest!) is non-existant in golang.

The only implementations of bcrypt (and crypt(3)) that I've seen that's NOT vulnerable to this are Golang and Python.

If the original poster / you do decide to go with golang I wish you the best.

I can compile (with 6g) the hello world example from golang.org with any brace indentation style.

All Golang needs to do is what Swift (just to name probably the closest analogue) does, with interfaces for runtime dispatch and generics for compile-time monomorphization.

My outlook for golang it strong - my concern is that you may drain away your runway doing what you should otherwise be doing on freetime.

Gorilla/context and alice are not mentioned by this article, but the lament a the end about the concept of context being lacking in golang is spot on.

I can tell you, in every category - at the present moment - golang's available libraries fall short to what you get in python.

In fact there was a rather inflammatory blog post[1] whose basic theme was that "Golang is trash" because the toolchain was so simple.

Between the concurrency, and php back in "one and done" mode the problem was "solved" and the internal team happily took over finishing the porting to pure Golang.

Not sure how much it applies here as I haven't looked at the code, but the Golang blog has a good article that talks about how to "Simplify repetitive error handling"[1].

We ingest and process hundreds of thousands of security events per second, using Kafka, Cassandra and Elasticsearch, Golang, Python and Scala.

We work with Golang, Node.js, AngularJS, Docker, and rkt.

I also have experience with Golang, React, Clojure, scipy, numpy, pandas, scikit-learn, nltk etc.