Viewing profile — circlespainter

I think it would be interesting to try http://docs.paralleluniverse.co/quasar/ too (fibers, and actors on top, for the JVM).

http://kotlinlang.org/ with http://docs.paralleluniverse.co/quasar/#preview-quasar-kotli...

> any library it's used with needs to be retrofitted/wrapped to make it work with Quasar. True, but 1/ to see how easy it can be to integrate a pre-existing library with Quasar, ju…

I'll only add that Quasar offers several types of "send" and "receive" operations: blocking indefintely, with timeout and even "try" variants that will not block at all, as well as…

If you want regular code and not async, then yes, it matters: if you have a lot of OS thread-based actors performing blocking network "send"s as part of their regular control flow,…

> I've been using Akka in combination with Scala's Futures, with Java 8's CompletableFutures, with Rx Observables, with in-house asynchronous queues and I can't see how Akka doesn'…

True, although it's a community project and not part of the main Akka project AFAIK. Worth mentioning though, thanks for pointing out.

In Akka an actor is basically a message handler; I personally think that being able to use regular control flow constructs is an easier way to model state machines than swapping ar…

By the way I'm the author of the post so feel free to get in touch, I'll be glad to answer any questions.

I don't agree but can you expand? Which parts are one-sided in your opinion and which other posts?

Can you expand on why you think these statements are not correct? I think they are thoroughly explained in the post.

Actually the statement about logging is a bit different and says that Akka offers an additional logging API, which is correct I believe, and I think this is unnecessary since a pre…

Actually bytecode manipulation doesn't make JVM alternative languages impossible, on the opposite Quasar allows them to be easily integrated and investigation/work is ongoing to av…