3 ms·
>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 pro
by antisemiotic 7y ago
>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 7y agoI know this, but I also know I struggled with C and Go felt delightfully straightforward.