csp

> "Libmill is intended for writing single-threaded applications." You can do concurrency on a single thread. This is the message I find it hard to get across when explaining CSP concurrency libraries. Some people argue about usefulness of such libraries as being not native and leaky abstraction. I developed Go-style concurrency "port" to Tcl: https://github.com/securitykiss-com/csp and it is one of few developed-in-house things that became the productivity booster in my toolbox. The interesting thing about it is that thanks to the expressive power of Tcl I was able to port not only the semantics but also almost completely mimic Go syntax.

I didn't believe I'd see the day when a larger Tcl project reaches HN front page. This looks really exciting and ambitious. John Ousterhout mentioned in one of the interviews that he regrets he didn't manage to produce the Tcl compiler while working in Sun. While in my day to day work I don't feel the need for the compiler (starkits are good enough) it might attract more performance concerned people to this powerful but forgotten language. For me returning to Tcl is always an immense pleasure. This is what it gives out of the box: - convenience of bash - power and elegance of Lisp - self-containing no-dependency nature of Go - clarity of Python - probably unique for the entire industry reliable cross-platform GUI toolkit - simplicity of Dodecalogue What Tcl is missing: - good handle on concurrency in bigger projects (with