Kilim – efficient java internal messaging

The internal messaging model used for concurrency in languages such as Erlang and Scala is undoubtedly compelling. Every time I try I get frustrated, though. I’m simply more comfortable with java. With this in mind I’m very interested in Kilim, which claims to provide a similar model usable directly from java, and with better performance than Scala.

Kilim

4 Comments

  1. A simple way to communicate between threads is to add tasks to a thread pool associated with each type of task. The thread pool comes with a work queue and a way to perform the work in a simple way.

  2. Why care if Kilim is successful Java framework or not, it has anyway taught us a new way of doing things in life. Come up with a Java framework, release it as open source and take credit from Java community. On the other hand, at the back force fit some E=mc2 theory to it and present it to University for getting a PhD degree, thereby killing two birds in one stone. Extremely smart, way to go!

    Universities anyway get free dollars from Uncle Sam, so they can afford to be Santa Claus to award PhDs to Java frameworks or perhaps to even product manuals!

    Research is no more about being selfless and working for benefit of mankind. It is about outsmarting the system to get a degree!

    “I never perfected an invention that I did not think about in terms of the service it might give others… I find out what the world needs, then I proceed to invent….” – Thomas Alva Edison

Comments are closed.