4 ms·

Hmm. I'm going to get crucified here but we've come up with a little language we call L (for little language. Really :) http://www.bitmover.com/lm/L.html htt

Hmm. I'm going to get crucified here but we've come up with a little language we call L (for little language. Really :) http://www.bitmover.com/lm/L.html http://www.bitmover.com/lm/L.html It's not really that interesting to most people, it was designed to be easy to read, easy to maintain larger programs in, in particular, it was designed to be easy to read and review, that was the point. It was not designed to be interesting to hackers like the folks here, I strongly suspect that 98% of you will go WTF? You based this on top of tcl? Are you retarded? And the answer is "well, yeah, sort of. But it fit our needs". Anyway, we're in the midst of a commercial product release but after that I can see about getting the source out for anyone who wants (BSD license or whatever tcl is, I know it's BSD or BSD like) as well as prebuilt images for all the common platforms (Windows, Mac, Linux, *BSD, HPUX, Solaris, AIX, even IRIX and SCO for the 3 people in the world still using those). If anyone has constructive feedback, bring it on. It's a moving target which is why we haven't released yet, haven't nailed down 1.0 hard enough that we want to live with it. We are using it internally.

bobds 16y ago
Interesting, what kind of projects have you written in L so far in your company? I actually started implementing a DSL in TCL a while ago, it was meant for a YubNub replacement but the project was scrapped and I never finished it.
- luckydude 16y ago
  We're reworking our GUI tools in it. Once it is really stable, we plan on provide a pile of canned triggers (email notification of commits, other workflow stuff) as part of our commercial product. And we have some plans for future products where L will be the glue that holds them together. An example would be a generic importer $SCM => BitKeeper written in L and shipped as source so that if you have some oddball SCM that we don't understand you can do your own importer. But the main point is to redo our guis. We're still playing around but this is an example - not polished yet but not as sucky as some stuff we've done in the past: http://bitmover.com/lm/explorer-l.gif http://bitmover.com/lm/explorer-l.gif

bobds 16y ago

Interesting, what kind of projects have you written in L so far in your company? I actually started implementing a DSL in TCL a while ago, it was meant for a YubNub replacement but the project was scrapped and I never finished it.

luckydude 16y ago
We're reworking our GUI tools in it. Once it is really stable, we plan on provide a pile of canned triggers (email notification of commits, other workflow stuff) as part of our commercial product. And we have some plans for future products where L will be the glue that holds them together. An example would be a generic importer $SCM => BitKeeper written in L and shipped as source so that if you have some oddball SCM that we don't understand you can do your own importer. But the main point is to redo our guis. We're still playing around but this is an example - not polished yet but not as sucky as some stuff we've done in the past: http://bitmover.com/lm/explorer-l.gif http://bitmover.com/lm/explorer-l.gif