Christopher Hunt

Thanks for including me in this conversation! On this point: > an actor pulls the next message from its mailbox — which may be done selectively, based on mailbox implementation...

On this: > In this view, an actor is nothing more than a stateful async function on top of a queue. An alternative formulation would be as an async handler...

> Taking a step back: Future + async/await is the standard Rust way of making something awaitable without blocking the current thread. If there were a similarly general incarnation of...

As an update to this case, we (Lightbend) are providing a reactive streams implementation via Akka streams here: https://github.com/typesafehub/akka-contrib-extra/pull/60.

Implementing the reactive streams API directly is tricky, as you've no doubt discovered. :-) While Akka streams will pull in undesirable dependencies for your library, there are other reactive streams...

We presently look for any js file in the app/assets/javascripts folder and put them through the closure compiler - we also ignore files starting with an "_". Any js file...

My first reaction is to the memory footprint of an application. Most of my Scala apps depend on some Java library. Therefore, the idea of an independent runtime makes me...

Do you have the same problem using less outside of sbt-web?

This can be achieved but I'll have to look at the plugins settings and get back to you. Please note though that by convention, app/assets denotes source assets to be...

Please note the last para of the README: > Options can be specified in accordance with the JSHint website and they share the same set of defaults. To set an...