13 ms·
How about we just use actors instead? Preemptable actors are the only good concurrency model I've ever come across. Everything else has massive problems
by smabie 6y ago
How about we just use actors instead? Preemptable actors are the only good concurrency model I've ever come across. Everything else has massive problems
- mgraczyk 6y agoAsync await scales well to codebases with millions of lines and thousands of developers. As a result, large companies and ecosystems have mostly adopted async/await and the tooling and runtimes in those languages is now much more mature.
- pansa2 6y ago> Async await scales well to codebases with millions of lines Interesting - do you think there's a better solution than async-await for smaller codebases?
- CraigJPerry 6y agoActors aren’t a panacea either - your logic ends up more spread out. You’re still able to shoot yourself in the foot quite easily too, e.g. when deciding whether to use a “pull” or “push” model for concurrency. I found async testing in python to be annoying, although i found a couple of libraries to make it nicer (pytest-async and i forget the name of the other).
- odiroot 6y agoI never understood this whole "actor" thing until I had to write an extension for Mopidy. Then it really clicked with me. It's very boilerplate-y (Mopidy uses Pykka) though and takes some time getting used to coming from other frameworks.