Re:Some thoughts on asynchronous Python API design in a post...
by lmm on Monday November 07, 2016 @04:30AM
(#12889828)
I use Scala without Akka. Just straightforward Futures and for/yield. It's great: the distinction between "=" and "<-" is minimal overhead when writing, but enough to be visible when reading code. You have to learn the tools for gathering effects (e.g. "traverse"), but you only have to learn them once (and they're generic for any effect, rather than being specific to Future, you can use the exact same functions to do error handling, audit logs and the like).
[ Parent
| on HN ]
Re:Some thoughts on asynchronous Python API design in a post...
by mi100hael on Monday November 07, 2016 @03:40PM
(#12894827)
After using Akka-HTTP, I never want to write a HTTP service with anything else.
Re:Some thoughts on asynchronous Python API design in a post...
by lmm on Tuesday November 08, 2016 @04:46AM
(#12898910)
akka-http is nice. akka-actor (i.e. the project that was originally called "akka") is awful. The name overlap is unfortunate.
Re:Some thoughts on asynchronous Python API design in a post...
by jscholes on Tuesday November 08, 2016 @06:26AM
(#12899350)
In your opinion, what's wrong with akka-actor?
Re:Some thoughts on asynchronous Python API design in a post...
by lmm on Wednesday November 09, 2016 @10:14AM
(#12910792)
It sacrifices type safety without offering enough value to be worth that - especially given that the model also eliminates useful stack traces. It forces non-distributed applications to pay the price of an API designed for distributed ones. Its FSM model doesn't offer the conciseness it should.