zlacker

>>welder+(OP)
modern programming languages should have enough concurrency primitives for building such systems. the python situation is out of control. we have bazillion of libraries and packages doing the same thing. with slight variations.

this very effort is deserves praising. but i have seen it happen many times before. dramatiq, huey, rq, schedule, etc. all one needs to do is wait for those pesky corner cases to start piling up. and maintainers being unable to solve them. or not solve them fast enough.

we need primitives, building blocks, to build such systems when needed. we need more control.

i like what golang does.

>>blondi+Gf
Language primitives aren't a substitute for a distributed queue service. You want stuff like persistence, scale-out, and retries if a node falls over and doesn't come back.

Something like Erlang's OTP might have suitable primitives, but only because it's already a distributed system.