3 ms·
Including Bayes in the standard library is cool, but newLISP must be one of the slowest LISP interpreters out there. Its certainly useable - usually on par wit
by shakna 10y ago
Including Bayes in the standard library is cool, but newLISP must be one of the slowest LISP interpreters out there.
Its certainly useable - usually on par with Python... But picolisp, Gambit, SBCL are more on par with D or Rebol.
So when newLISP claims to be great for embedding, I feel cautious.
- tluyben2 10y agoFor me Picolisp is a very nice Lisp implementation; easy to understand, enthused founder who has been at it since the 80s. Which is amazing in it's own right. And a solid community. Won't go away any time soon. Gambit is the same age, but I find the source code far harder to read. That's a matter of taste I guess.
- shakna 10y agoF-Expressions are awesome fun. Gambit internals does kind of look like black magic half the time, but the author implemented environments because I asked [0], which is very cool. The more experimental lisps, the better we can make the future. I love how the lispish community views PLT, and always tries out someone's new idea. (Bayes integration in newLISP is cool. LFE is also cool.) [0] https://github.com/gambit/gambit/issues/204 https://github.com/gambit/gambit/issues/204
- eggy 10y agoDitto on Fexprs, and PicoLisp! Xtlang in Extempore is a whole lot of fun [1]. Echolisp has amazing built-ins and runs in the browser [2]. Gambit is great to get C code out of. I like LFE, but I have to learn more OTP/BEAM to really use it. Wasp Lisp is a lot of fun for me, and for playing with distributed programs. [1] http://extempore.moso.com.au/ http://extempore.moso.com.au/ [2] http://www.echolalie.org/echolisp/ http://www.echolalie.org/echolisp/
- shakna 10y agoHadn't heard of Wasp [0] before. Looking forward to trying it out! [0] https://github.com/swdunlop/WaspVM https://github.com/swdunlop/WaspVM
- qwertyuiop924 10y agoHave you tried Kernel?
- freekh 10y agoFexprs should be fun, it stands for fun-expression after all... Right?.. I am not a lisper though...:D
- qwertyuiop924 10y agoNo, although what it stands for has been lost to the ages. They're functions whose args are passed unevaled. It kills a whole variety of compiler optimizations, but in an interpreter, there's no reason not to have them.
- minikomi 10y agoHow much of an issue does fixed point over floating point become in picolisp?
- throwaway7645 10y agoMy only criticism (not really criticism)is that Windows is only supported through Cygwin. I will say you can tell the community is very competent. 9/10, the picolisp example on RosettaCode is the most readable while being in the top 5 shortest for loc (kind of hard to beat J in loc).
- kazinator 10y agohttp://www.kylheku.com/cygnal/ http://www.kylheku.com/cygnal/
- deleted 10y ago[deleted]
- throwaway7645 10y agoD is more like C++ and I guess SBCL isn't too far from that realm in some cases (certainly slower in most). Rebol, python, and picolisp are all interpreted though and quite slow by comparison.
- shakna 10y agoSBCL really isn't that slow [0], being on par if not faster than Java in most things. Python is a magnitude of order slower [1] than most things, and that was my point. newLISP is slow. I do have to take exception to you calling interpreted slow - because you've called Python interpreted, I'm guessing bytecode interpreted fits your view. Picrin [2] is bytecode interpreted, and isn't slow. [3] By Rebol I mostly meant Red, which isn't exactly slow, as it aims for 1-3x the speed of C. (Though I can't find any decent set of benchmarks for it currently). [0] https://benchmarksgame.alioth.debian.org/u64q/lisp.html https://benchmarksgame.alioth.debian.org/u64q/lisp.html [1] http://benchmarksgame.alioth.debian.org/u64q/python.html http://benchmarksgame.alioth.debian.org/u64q/python.html [2] https://github.com/picrin-scheme/picrin https://github.com/picrin-scheme/picrin [3] http://www.larcenists.org/benchmarksGenuineR7Linux.html http://www.larcenists.org/benchmarksGenuineR7Linux.html
- igouy 10y ago> Picrin is bytecode interpreted, and isn't slow. [3] Those measurements seem to show Picrin at-least an order of magnitude slower than Larceny?
- shakna 10y agoYep. Larceny is one of the fastest compiled Schemes. Doesn't mean Picrin is slow, though. It matches Chicken in most of the stats, and Chicken uses the same process (Cheney on the MTA), but Chicken is compiled. Picrin is bytecode interpreted.
- dfox 10y agoThe whole newLISP semantics (everything dynamic, no closures) serves for it to be one of the fastest pure interpreters out there. IIRC it is even significantly faster than CPython (on microbenchmarks). The reason for that lies in the fact that newLISP's interpreter does not have to do that much of pointer chasing as other interpreters which implement some kind of lexical scoping. In dfsch I found out that about 80% of time is spent in symbol-lookup related code and had to resort to some ugly tricks (inlining constant references in AST, microoptimalizations in lookup code...) to get it's performance to be somewhere between CPython and newLISP.