2 ms·
I'm not sure if it's just me, but after years of writing Python code with various async I/O libs and then used Go for a while, it felt so much better when the l
by riobard 13y ago
I'm not sure if it's just me, but after years of writing Python code with various async I/O libs and then used Go for a while, it felt so much better when the language/runtime handles async I/O for me and I do not have to think about event loops at all.
Python used to be the clean and simple language for me, but all those ”hacks” to get async right just makes the final code ugly. The cleanness of Go wins me over instantly.
Even though the two languages are not directly comparable, the foundations of Go seems to me much better and solid. It reminds me of Rob Pike's essay “Less is exponentially more” http://commandcenter.blogspot.ca/2012/06/less-is-exponentially-more.html http://commandcenter.blogspot.ca/2012/06/less-is-exponential...
- natmaster 13y agoTry gevent or eventlet. Real pythonistas use these, instead verbose java-esque coroutines.
- coldtea 13y agoTo paraphrase JWZ, "Python is big because your needs are big". I don't see anything "hacky" to get async right. It's a simple library. It's just not first class (then again, no reason it should be, isn't it not first class in Rust too?).