News for hackers. Stuff that matters.
Re:NewLisp by kazinator on Friday September 25, 2015 @03:16PM (#10280108)
NewLisp was designed by a psychologist, who took meticulous care to endow it with design elements such that it would be instantly hated and denounced by anyone who has had anything to do with real Lisp, causing them to spew babble that is incomprehensible to NewLisp n00bies, save for the lingering perception that something gratuitously negative has been spoken. This, in turn, has the calculated effect of making them dig deeper into their trenches.

It is best to remain silent upon the subject of the NewLisp design. Let people make their bed and lie in it.

By the way, if you want to see a really crazy NewLisp zealot, search for Kazimir Majorinc. Wow ...

Maybe he's quit since (and even reformed?); it's been a few years.

> Changing the binding time for free variables within a closure

What closure? NewLisp has done away with those, and offers "name space contexts"

http://www.newlisp.org/index.cgi?page=Closures

These are basically something like modules with static variables.

Re:NewLisp by JeremyReimer on Friday September 25, 2015 @03:43PM (#10280245)
I'm not sure it's fair to tar all newLISP advocates with the same brush. I understand the design choices that Lutz Mueller made, and I can understand how they might be considered unsatisfactory by other Lisp users. That's fine-- I don't expect newLISP to be everything to everybody, and I don't consider it to be the be-all and end-all of languages.

I do find it to be very lightweight and flexible, with excellent documentation and a good built-in library. This makes it useful as a scripting language and for rapid prototyping. I wouldn't recommend it for very large-scale tasks or for projects developed by large teams.

Re:NewLisp by kazinator on Friday September 25, 2015 @04:43PM (#10280560)
> I don't expect newLISP to be everything to everybody, and I don't consider it to be the be-all and end-all of languages.

Lutz Mueller does. For instance, quote: LISP is an old language born, grown, and standardized in times very different from today, times when programming was for highly educated people who engineered programs. newLISP is LISP reborn as a scripting language: pragmatic and casual, simple to learn without requiring you to know advanced computer science concepts.

Sure, no advanced computer science concepts: just five different hacks to choose from to do some aspect of what a lexical closure does. (Just pick the one whose assumptions are least likely to break in your use case: but no engineering knowledge required to do that, nope!)

NewLisp requires the users to absorb advanced concepts that have fallen by the wayside of the computer science mainstream. A fexpr or self-modifying code are still computer science concepts.

Basically what Lutz is the real problem in NewLisp; other than that, the thing is what it is, take it or leave it. More than needing a compiler, garbage collection or lexical closures, it just needs a dose of humility, really.

On that note, it's somewhat good to see that a lot of the anti-Lisp ranting has been toned down compared to just several years ago. I don't get the sense that Lutz is yet eating any real crow. At best, he's pouring crow-flavored syrup over his ice cream. But at least that's a start!

Re:NewLisp by agumonkey on Friday September 25, 2015 @03:35PM (#10280206)
Haha, indeed that pattern is fun. It reminds me of people using placeholders in BASIC source to store state. I'm not sure I'm reading right.