How newLisp Took My Breath (And Syntax) Away
taoeffect.com
How newLisp Took My Breath (And Syntax) Away
1–10 of 35 posts
Re: How newLisp Took My Breath (And Syntax) Away
#2> and extra stuff can be accessed through the function (args) or the symbol $args.
Hmm.. what makes $args a symbol? The sigil? If not, what does the sigil $ indicate? Isn't that syntax? Why isn't it listed here: http://www.taoeffect.com/blog/wp-content/uploads/2009/12/new... ?
Re: How newLisp Took My Breath (And Syntax) Away
#3> and extra stuff can be accessed through the function (args) or the symbol $args. Hmm.. what makes $args a symbol? The sigil? If not, what does the sigil $ indicate? Isn't that syntax? Why isn't it listed here: http://www.taoeffect.com/blog/wp-content/uploads/2009/12/new... ?
The '$' is just another character. $args is a symbol defined by newLISP, which uses the $ character as a convention to indicate system symbols:
http://www.newlisp.org/downloads/newlisp_manual.html#system_...
Re: How newLisp Took My Breath (And Syntax) Away
#4Good article, I've liked newLISP since I discovered it a few days ago but wasn't sure about it after a few responses to my comment in the newLISP webframework thread...
It can easily become a python replacement for me!
Re: How newLisp Took My Breath (And Syntax) Away
#5The opinion of those who know significantly more than me is that newLisp is to be avoided.
http://news.ycombinator.com/item?id=788157
In most anything written by a fan of newLisp, you'll find something like the following (taken from the linked article):
> Today, unfortunately, whenever someone mentions newLISP on an online forum frequented by adherents of another LISP, an almost clan-like flame war will erupt. An adherent of one particular dialect, usually someone who has never used newLISP, will shout obscenities such as, "newLISP goes back on just about every advancement made by LISPs", or "dynamic scope is evil!"
Maybe there's something to newLisp, but any time I see a group with that flavor of persecution complex ("All the criticism is wrong because they just don't understand!") I take pause.
Re: How newLisp Took My Breath (And Syntax) Away
#6I'd like to see some detail on how the project was done in order to allow us to judge the syntax ourselves. The examples provided aren't very detailed. Perhaps a code snippet or two would help. I'd especially like to see how the graphics were done.
Re: How newLisp Took My Breath (And Syntax) Away
#7The opinion of those who know significantly more than me is that newLisp is to be avoided. http://news.ycombinator.com/item?id=788157 In most anything written by a fan of newLisp, you'll find something like the following (taken from the linked article): > Today, unfortunately, whenever someone mentions newLISP on an online forum frequented by adherents of another LISP, an almost clan-like flame war will erupt. An adh…
Maybe there's something to newLisp, but any time I see a group with that flavor of persecution complex ("All the criticism is wrong because they just don't understand!") I take pause.
I think there was more to it than that. :-)
Re: How newLisp Took My Breath (And Syntax) Away
#8The opinion of those who know significantly more than me is that newLisp is to be avoided. http://news.ycombinator.com/item?id=788157 In most anything written by a fan of newLisp, you'll find something like the following (taken from the linked article): > Today, unfortunately, whenever someone mentions newLISP on an online forum frequented by adherents of another LISP, an almost clan-like flame war will erupt. An adh…
I guess you can view newLISP in at least two different ways: a naive implementation of it, or a reboot of it, branching from a much older LISP than most today do.
I think of the new LISPs out there, Clojure has its act together much more than newLISP - it's quite sophisticated in a lot of ways, it's making rapid progress, and now has a relatively large development community for such a new language.
But for newLISP users: if it works, it works, and more power to you.
Re: How newLisp Took My Breath (And Syntax) Away
#9The opinion of those who know significantly more than me is that newLisp is to be avoided. http://news.ycombinator.com/item?id=788157 In most anything written by a fan of newLisp, you'll find something like the following (taken from the linked article): > Today, unfortunately, whenever someone mentions newLISP on an online forum frequented by adherents of another LISP, an almost clan-like flame war will erupt. An adh…
Step 0: don't pretentiously prepend "new" to the name of your language.
Re: How newLisp Took My Breath (And Syntax) Away
#10The opinion of those who know significantly more than me is that newLisp is to be avoided. http://news.ycombinator.com/item?id=788157 In most anything written by a fan of newLisp, you'll find something like the following (taken from the linked article): > Today, unfortunately, whenever someone mentions newLISP on an online forum frequented by adherents of another LISP, an almost clan-like flame war will erupt. An adh…
Maybe there's something to newLisp, but any time I see a group with that flavor of persecution complex ("All the criticism is wrong because they just don't understand!") I take pause. I think there was more to it than that. :-)
I haven't read (in your article or elsewhere) sufficient defense for newLisp's choice of
o Lazy evaluation ("fexprs") over Lisp macros
o "One-Reference-Only" memory management over garbage collection
o Dynamic scope over lexical scope
But you've found it "the easiest [Lisp] to setup, deploy, and develop for"? Great! newLisp has fantastic documentation and a helpful community? Perfect! I full-heartedly agree with zephjc: "if it works, it works, and more power to you."