Re:Why I Switched from Python to Clojure (2016)
by benatkin on Sunday March 24, 2019 @03:49PM
(#19478378)
Python's async support also seems to be getting better. There's a flask clone called Quart (http://pgjones.gitlab.io/quart/) and an async postgres client (https://github.com/MagicStack/asyncpg). It works very similar to JavaScript, with async and await keywords. I think it should provide speed and comfort especially if you're a regular JavaScript user.
[ Parent
| on HN ]
Re:Why I Switched from Python to Clojure (2016)
by Waterluvian on Sunday March 24, 2019 @04:38PM
(#19478610)
I wrote a pretty substantial experiment using asyncio for 100k websocket client connections across a massive theoretical fleet of robots. It's not open source but the general result was that I used to hate async in Python and now I love it.
The syntax makes blending sync and async easy. And the cooperative multitasking paradigm is very easy to reason about. No locks!
Re:Why I Switched from Python to Clojure (2016)
by simple_phrases on Sunday March 24, 2019 @06:41PM
(#19479185)
If you did a write-up or went into more detail about your experience, I'd read it.
Big fan of Python and am heavily invested in its ecosystem, but I currently prefer async programming in modern JavaScript compared to Python.
Did you make use of third-party async libraries?
Re:Why I Switched from Python to Clojure (2016)
by Waterluvian on Sunday March 24, 2019 @06:48PM
(#19479217)
I'm going to ask my boss to open source it and then do a write up.
Re:Why I Switched from Python to Clojure (2016)
by j88439h84 on Sunday March 24, 2019 @07:21PM
(#19479331)
Python is even better since it has http://trio.rtfd.org which provides structured concurrency.