[tomlock]

I have very little experience in compiled languages. Coming to Go after Python was not only a joy, but I was able to easily implement concurrency and improve the performance of my game of life simulation side project by something like 25x.

So to me it feels like they did something right.

I guess maybe there just sometimes being a way to do something right only one way, makes searching for solutions, easier. I contrast that with another language I love, Ruby, where it can sometimes feel like there are so many ways to do things that the language isn't opinionated at all.

[antisemiotic]

>Coming to Go after Python was not only a joy, but I was able to easily implement concurrency and improve the performance of my game of life simulation side project by something like 25x.

Python is notoriously bad at both these things though, so it's not a very high bar. I think a more meaningful comparison would be to languages like Clojure, Erlang/Elixir, Rust, or any other that has concurrency as one of the top priories, but makes different tradeoffs.

[tomlock]

I know this, but I also know I struggled with C and Go felt delightfully straightforward.