2 HN users recommended this talk2 months2009–2012score 2
Years with an HN recommendation, 2007–2026
Pointed to as evidence that Java can do fast, cheap message-passing concurrency, as an alternative to Erlang or Scala actors.
A Google Tech Talk by the author of Kilim, a Java library for lightweight actor-style message passing. It argues that message passing can replace shared-memory concurrency and claims performance competitive with or better than Erlang for huge numbers of actors.
“Kilim's author did a nice Google Talk” (HN, 2009)
Actors are decoupled from the means by which they are executed. Scala has a nice system where you can run thousands of event-based actors in a thread pool. It grows the pool as needed (as threads block). See [link] While it may use threads, Scala's actor system effectively allows you to create thousands of actors. Kilim is actually a pure (depending on whether you see a byte-code processing system as pure) Java system that does the same thing (as far as I can tell): [link] Kilim's author did a nice Google Talk: [this video] EDIT: Fixed some grammar and added video link.
Kilim author's Google talk on lightweight actors in Java.
"Asynchronious message passing is old and great idea. Instead of synchronizing objects and dealing with deadlocks we try to isolate objects and let them exchange messages. Erlang proved it to be extremly powerful tool applicable to wide range of highly scalable mission critical applications. In JVM landscape big interest to this approach started after introducing Scala actors. " That statement is so very poorly informed! JMS ("surprise"?) has been a sign of "interest" in "Asynchronious message passing" in the "JVM landscape". I am not up on my Scala, but the author fails to convey (based on what I do know ;) the competence level that would lend weight to his attempt to address (much less support) the topic. For those interested in other JVM alternatives, Kilim seems quite promising and seems to hold its own quite well in benchmarks against Erlang. [link] [this video] [link] [scroll to end to see the impressive results for Kilim.] [link] [edit: added pdf link]
Kilim as a promising JVM message passing alternative competitive with Erlang.
SPEED :: In defence of Java, it is very quick when done right. See Kilim[1] for examples. SUPPORT :: On top of the speed Java has a supported hardware stack (Solaris). So if doing 100K connections is important to you, you can find engineers who can diagnose difficult problems on your whole stack. -------------- [1] [this video] at 23:23 . Java is quick without Kilim too, this is just an example with stats.
Kilim talk showing Java message passing can be very fast.
Erlang is a CSP system, first and foremost, and not actors. [CSP style concurrency on JVM]: [this video] (Kilim, it should be noted, was benchmarked as scaling better than Erlang/OTP.) [link] (paper in top comment is worth the read.) Disclaimer: I think Erlang/OTP rocks. But JVM has its moments, as well, and in fairness has earned the "most advanced VM" title.
Video list and Hacker News comment labels from HackerTube (prompted by @karpathy), released under ODC-By 1.0, built on the open-index/hacker-news archive. Hacker News data is provided by Y Combinator; comments remain the work of their authors. Video titles, channel names and thumbnails belong to their creators and are shown via YouTube. HackerTube Watch is an unofficial edition. Data export of 2026-10-31.
Plays via YouTube's privacy-enhanced embed
4 Hacker News comments
From the HN archive; up to 20 kept per video, favoring different commenters. Recommendations first.
Read more
Citations, criticism and jokes