Jim Tcl version 0.78
jim.tcl.tk
Jim Tcl version 0.78
1–10 of 26 posts
Re: Jim Tcl version 0.78
#2I started this project many years ago, and later abandoned it. Fortunately the project found another gentle and capable father that developed it for years and put it into a useful niche: embedded systems. However Jim Tcl is still, for me, a milestone of my programming life. It was the first time that, inspired by the Tcl internals, I started to realize how to write clean C code using better abstractions. It's awesome to see the project still alive, thank you Steve.
Re: Jim Tcl version 0.78
#3I started this project many years ago, and later abandoned it. Fortunately the project found another gentle and capable father that developed it for years and put it into a useful niche: embedded systems. However Jim Tcl is still, for me, a milestone of my programming life. It was the first time that, inspired by the Tcl internals, I started to realize how to write clean C code using better abstractions. It's awesome…
> Jim is supported. If you need commercial software, contact the original author at 'antirez@gmail.com' or the current maintainer at 'steveb@workware.net.au'.
Do you get many support emails, still?
Re: Jim Tcl version 0.78
#4I started this project many years ago, and later abandoned it. Fortunately the project found another gentle and capable father that developed it for years and put it into a useful niche: embedded systems. However Jim Tcl is still, for me, a milestone of my programming life. It was the first time that, inspired by the Tcl internals, I started to realize how to write clean C code using better abstractions. It's awesome…
I always wondered why you used lua embedded into redis instead of tcl? Has that been written about before?
Re: Jim Tcl version 0.78
#5I started this project many years ago, and later abandoned it. Fortunately the project found another gentle and capable father that developed it for years and put it into a useful niche: embedded systems. However Jim Tcl is still, for me, a milestone of my programming life. It was the first time that, inspired by the Tcl internals, I started to realize how to write clean C code using better abstractions. It's awesome…
For the Tcl internals, was this John Ousterhout's code or some other codebase? Have you read his new (ish) book on Software Design? [1]
[1] https://www.amazon.com/Philosophy-Software-Design-John-Ouste...
Re: Jim Tcl version 0.78
#6I started this project many years ago, and later abandoned it. Fortunately the project found another gentle and capable father that developed it for years and put it into a useful niche: embedded systems. However Jim Tcl is still, for me, a milestone of my programming life. It was the first time that, inspired by the Tcl internals, I started to realize how to write clean C code using better abstractions. It's awesome…
For the Tcl internals, was this John Ousterhout's code or some other codebase? Have you read his new (ish) book on Software Design? [1] [1] https://www.amazon.com/Philosophy-Software-Design-John-Ouste...
Yep it was the original JO code base, but I think that when I read it (it was already Tcl 8) a lot of other people had rewritten major parts, but the standard and quality were set I guess, and also the core team was composed of people that knew how to write code. About the new book: ordered it via Amazon, but Amazon Italy for some time now for small things use the local postal service, that always fails, so it returned back... to Amazon. I'll have to purchase it again.
Re: Jim Tcl version 0.78
#7I started this project many years ago, and later abandoned it. Fortunately the project found another gentle and capable father that developed it for years and put it into a useful niche: embedded systems. However Jim Tcl is still, for me, a milestone of my programming life. It was the first time that, inspired by the Tcl internals, I started to realize how to write clean C code using better abstractions. It's awesome…
> Jim is supported. If you need commercial software, contact the original author at 'antirez@gmail.com' or the current maintainer at 'steveb@workware.net.au'. Do you get many support emails, still?
Not much but a few questions from time to time, I don't reply most of the times unfortunately... I receive a lot more emails about hping (!).
Re: Jim Tcl version 0.78
#8I started this project many years ago, and later abandoned it. Fortunately the project found another gentle and capable father that developed it for years and put it into a useful niche: embedded systems. However Jim Tcl is still, for me, a milestone of my programming life. It was the first time that, inspired by the Tcl internals, I started to realize how to write clean C code using better abstractions. It's awesome…
I always wondered why you used lua embedded into redis instead of tcl? Has that been written about before?
Because I thought it was not a good idea to script Redis using an opinionated language as Tcl. Lua is a lot more "algol like", more understandable to the casual script writer.
EDIT: However there is an even more important thing that resembles Tcl in Redis: the commands you send to the server to alter the data set are very similar to Tcl commands.
Re: Jim Tcl version 0.78
#9Earlier quoted context omitted.
I always wondered why you used lua embedded into redis instead of tcl? Has that been written about before?
Because I thought it was not a good idea to script Redis using an opinionated language as Tcl. Lua is a lot more "algol like", more understandable to the casual script writer. EDIT: However there is an even more important thing that resembles Tcl in Redis: the commands you send to the server to alter the data set are very similar to Tcl commands.
there is no such thing as casual redis script writer
if you are technical enough to write scripts for redis, you are not casual
Re: Jim Tcl version 0.78
#10I started this project many years ago, and later abandoned it. Fortunately the project found another gentle and capable father that developed it for years and put it into a useful niche: embedded systems. However Jim Tcl is still, for me, a milestone of my programming life. It was the first time that, inspired by the Tcl internals, I started to realize how to write clean C code using better abstractions. It's awesome…
Why is it called "Jim"?