News for hackers. Stuff that matters.
Re:Why Lisp? (2015) by libx on Tuesday October 26, 2021 @07:46PM (#29007904)
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...

Re:Why Lisp? (2015) by lanstin on Tuesday October 26, 2021 @08:04PM (#29008036)
Lisp compiles to native code, TCL is forever parsing the strings it passes around.
Re:Why Lisp? (2015) by kevin_thibedeau on Tuesday October 26, 2021 @08:13PM (#29008094)
> 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.

Re:Why Lisp? (2015) by lanstin on Tuesday October 26, 2021 @11:58PM (#29009390)
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.
Re:Why Lisp? (2015) by pjmlp on Wednesday October 27, 2021 @08:08AM (#29012121)
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.
Re:Why Lisp? (2015) by pjmlp on Wednesday October 27, 2021 @08:09AM (#29012131)
Tcl is quite nice, having been part of a product similar to AOL Server, I never got the hype around Rails.