hoplon

2025-11-08T14:02:10.451999Z

here's something I've been working on lately that's vaguely hoplon adjacent: https://github.com/tailrecursion/chasma

chromalchemy 2025-11-09T00:00:36.401799Z

Interesting. I don’t know much about concurrency approaches, but sounds powerful if it simplifies things. Can you comment on how its adjacent to hoplon? I wonder if it has anything in common with this recent behavioral threads approach? https://thomascothran.tech/2024/10/a-new-paradigm/ https://github.com/thomascothran/pavlov

2025-11-09T03:37:51.048799Z

The apis are similar in that it doesn’t impose a naming scheme. You use vars and let bindings like with regular lisp

2025-11-09T03:38:19.057989Z

Compared to many other approaches in Java world and in apps I’ve seen that are oriented around a static topology

2025-11-09T03:39:08.582639Z

It both also supports a relevant concept of transaction, similar to the way javelin cells support watches and the way javelin transactions work

2025-11-09T03:42:21.515259Z

There’s a link to a great talk here as well as other references may be interesting https://github.com/dbmcclain/Lisp-Actors/issues/6

2025-11-09T03:44:33.483129Z

Bthreads, cool, and somewhat actor-y

2025-11-08T14:03:06.668909Z

would love to hear any thoughts. of note is on-commit! which lets you do at-most-once code in your behaviors, making it possible to dump results into other tools/systems