Ah, if newLISP had only dispensed with the "new" and "lisp" in its name, it might be viewed in an entirely different vein. Alas, it did not and thus nearly committed language seppuku. As to the language itself, as a casual programmer I very much like it. Its use is clear, it's well documented, and it's self-contained (and thus easily installed).
newLISP v.10.7.4 Development Release
21–22 of 22 posts
Re: newLISP v.10.7.4 Development Release
#22newLISP was the butt of half the jokes on #scheme over a decade ago. I'm surprised it had enough uptake to stick around. Uniquely for a Lisp, all objects are deep-copied by value when passed around. It also doesn't have closures. To get around these and other limitations, it has a notion of contexts that are auto-dereferenced ("default functor calls") so you can pass values by reference with syntactic sugar. At least…
newLISP is a language to replace sh/bash/perl. I don't know of any other s-expression language targeting that space? The thing is, if you look at what people on various programming language channels mock, bash et al should be the target of widespread derision. It does everything "wrong" and is an absolute mess. Yet all of these languages do a really good job of being super simple to use when you quickly need to autom…