[libx]

Everyday there's at least a post about Lisp. But I see none about TCL that is as regular in syntax as Lisp. Some call it a Lisp without parenthesis.

TCL is also very stable between releases, it has industrial strength and threading support.

But it lacks advocacy. It could get one tenth of what Lisp gets...

[lanstin]

Lisp compiles to native code, TCL is forever parsing the strings it passes around.

[kevin_thibedeau]

> TCL is forever parsing the strings it passes around.

No it isn't. Tcl has had dual-ported objects and a bytecode interpreter for over 20 years.

[lanstin]

Well I learned something. But if you represent a list as a lift of strings wouldn’t it have to parse them as Argv in the c implementation? It has been a while but only 17 years since I wrote TCL commands but each one started with a list of strings. Maybe the byte code interpreter doesn’t work with older C extensions? But the main selling point of TCL was easy extension.

[pjmlp]

Only if you were using the pre-Tcl 8 FFI API, our startup was built on a Tcl "Rails" similar to AOL Server, and we did plenty of native bindings.

[pjmlp]

Tcl is quite nice, having been part of a product similar to AOL Server, I never got the hype around Rails.