Re:Why do we need Flask, Celery, and Redis? (2019)
by jatone on Sunday April 19, 2020 @09:31AM
(#22915756)
and on top of it go is performant enough that 90% of the time you don't need them to begin with.
Re:Why do we need Flask, Celery, and Redis? (2019)
by hackworks on Sunday April 19, 2020 @10:16AM
(#22916067)
Most common use case for concurrency is for IO intensive workloads. When it comes down to IO, programming language hardly matters.
If you have CPU intensive workload, an optimizing compiler can help. Well, for that you have C or other languages with more mature and aggressive compilers.
(1) it's undersupported (e.g. you can in theory download s3 files using async botocore, but in practice it is hard to use because of strict botocore version dependencies)
(2) it isn't natural - once you're in the event loop it makes sense, but using an event loop alongside normal python code is confusing at best.
(3) it got introduced too late. The best async primitives are only available in pretty recent versions of python3.
The difference with go is that it go has these primitives built in from the beginning and using them doesn't introduce interoperability problems.