Arguments against newlisp (pro-SBCL)
Posted: Fri Aug 05, 2005 6:49 pm
Taken from a debate in the #newlisp channel on freenode, here was this guy's complaints/arguments:
<someguy> well, newlisp's memory manager really sucks
<someguy> because it doesn't handle shared structure
<someguy> it copies objects when you pass parameters
<someguy> because its inefficient
<someguy> also it means you can't have first-class arrays or hash tables
<someguy> you have to name all arrays and hashes by symbols, and pass symbols, you can't just pass an anonymous hash
<someguy> it severely limits the language
<someguy> performance?
<someguy> sbcl is much faster
<someguy> except the design of newlisp is quite poor
<someguy> and i noticed the flawed memory management, and lack of first-class arrays and hashes
<someguy> more problems in newlisp than high-quality common lisps like sbcl
<someguy> in fact, i don't see anything newlisp is good for
<someguy> i've also looked at the implementation code, its a mess
<someguy> in that sbcl is better in every way
<someguy> it has first class arrays, hashes, real gc, a better object system
<someguy> newlisp is a strict subset of common lisp, except the really broken parts (copying all values when passing parameters, 'contexts')
<someguy> also there's no number tower
<someguy> so integer math overflows
<someguy> that's really bad
<someguy> you can have a file larger than 2gb, but newlisp cannot represent its size
<someguy> algorithms like md5 and sha1 hashing, and rsa crypto all use bignums
I could argue all day with this guy, but in the end, I'm really only interested in Lutz's commentary. So if you wouldn't mind...
Thanks.
<someguy> well, newlisp's memory manager really sucks
<someguy> because it doesn't handle shared structure
<someguy> it copies objects when you pass parameters
<someguy> because its inefficient
<someguy> also it means you can't have first-class arrays or hash tables
<someguy> you have to name all arrays and hashes by symbols, and pass symbols, you can't just pass an anonymous hash
<someguy> it severely limits the language
<someguy> performance?
<someguy> sbcl is much faster
<someguy> except the design of newlisp is quite poor
<someguy> and i noticed the flawed memory management, and lack of first-class arrays and hashes
<someguy> more problems in newlisp than high-quality common lisps like sbcl
<someguy> in fact, i don't see anything newlisp is good for
<someguy> i've also looked at the implementation code, its a mess
<someguy> in that sbcl is better in every way
<someguy> it has first class arrays, hashes, real gc, a better object system
<someguy> newlisp is a strict subset of common lisp, except the really broken parts (copying all values when passing parameters, 'contexts')
<someguy> also there's no number tower
<someguy> so integer math overflows
<someguy> that's really bad
<someguy> you can have a file larger than 2gb, but newlisp cannot represent its size
<someguy> algorithms like md5 and sha1 hashing, and rsa crypto all use bignums
I could argue all day with this guy, but in the end, I'm really only interested in Lutz's commentary. So if you wouldn't mind...
Thanks.