4 ms·
Akka looks pretty sweet, but it looks like you still have to worry about blocking code in external libraries. In Haskell (and Erlang, IIRC), blocking code is de
by pjscott 15y ago
Akka looks pretty sweet, but it looks like you still have to worry about blocking code in external libraries. In Haskell (and Erlang, IIRC), blocking code is deferred to a background thread automatically so you don't have to be consciously on-guard for it. You also get proper pre-emptive multithreading, while Akka looks like a hybrid of an event loop and a thread pool.
Is this a substantial headache with Akka, in practice?
- gtani 15y ago(late reply) it's pretty hard to google akka deployments but: http://www.quora.com/What-companies-are-using-Akka-commercially-and-which-features-are-they-using http://www.quora.com/What-companies-are-using-Akka-commercia... http://groups.google.com/group/akka-user/browse_thread/thread/6e10174ac8bd9c4f?pli=1 http://groups.google.com/group/akka-user/browse_thread/threa... and in terms of memory overheads and how many erlang process-type things you can spin up: http://akka.io/docs/akka/1.1/scala/tutorial-chat-server.html http://akka.io/docs/akka/1.1/scala/tutorial-chat-server.html