5 ms·
Lush's heyday was the 01990s, and it's pretty much only useful for "scientific computing", which has a big overlap with "machine learning". Also, it's a Lisp.
by kragen 5y ago
Lush's heyday was the 01990s, and it's pretty much only useful for "scientific computing", which has a big overlap with "machine learning". Also, it's a Lisp. Python has more readable syntax and was used for all sorts of things even before Numpy existed.
- thewakalix 5y ago> 01900s Preparing for Y10K? That's exceptionally long-termist.
- MonkeyClub 5y agoCan't even make an octal joke with that 9 in there...
- kragen 5y agoHey, 9 is an octal digit in K&R C!
- stewbrew 5y agoI think we have to distinguish between languages that use s-expressions and lisps. Almost all languages have some sort of preprocessor that make it look like lisp but that doesn't turn it into lisp. From what I vaguely remember, lush lacked some of the defining qualities of a lisp.
- webreac 5y agoIn my lessons about scheme (given by the french translator of TAOCP), I have the following essential characteristics: - static binding - closures (true) - tail recursion - garbage collector s-expression or typing is a matter of choice, but, IMHO, if you lack one of the four previous items, it is not really a lisp.
- alpaca128 5y agoEmacs Lisp doesn't have tail call optimization, just like the Lisp it was inspired by. I'm definitely not an expert in that area, but this list seems kind of arbitrary to me. Especially with s-expressions being optional, which are probably the widest-known feature of the language. According to that definition, Haskell is a "true" Lisp but at least 2 Lisps are not. That makes no sense to me.
- webreac 5y agoThe last sentence was from me. The four items are from the SICP (not TAOCP, my mistake). They all are mandated by IEEE scheme standard. I have encountered many functionnal languages when I was student (caml-light (the ancestor of ocaml), lelisp, gofer (a cousin of haskell), miranda, graal, FP systems, yafool). The typing may be dynamic or static. The evaluation may be strict or lazy. They may have homoiconicity or a more suggared syntax. All theses choices are valid. These languages have in common the list of fundamental properties. IMHO, this list of 4 items encompass many aspects of SICP. When I evaluate a language, this list helps me understand the qualities and limitations of a language. For example, Perl5 does not have a true garbage collector. javascript does not have tail recursion. Knowing these limitations, I will not code the same way. In Perl5, I will take care of breaking unused circular data. In javascript, I will reorganise highly recursive algorithms.
- nicoburns 5y agoJavaScript does have tail recursion in the spec, and JSC (Safari) implements it. Other runtimes have thus far refused to because it can impact on debugging I believe.
- stewbrew 5y agoAlmost every language can do tail recursion (in most languages it will blow the stack though) but not every language does tail call optimization. This is a requirement for scheme but it is not for common lisp and many other lisps. So, I don't think this should be on the list.
- 5y ago
- kragen 5y ago"Lush" stands for "Lisp Universal Shell". It has not just S-expression syntax but recursion, setq, dynamic typing, quoting of S-expressions and thus lists and homoiconicity, cons, car, cdr, let*, cond, progn, runtime code evaluation, serialization (though bread/bwrite rather than read/print), and readmacros. Its object system is based on CLOS. Lush is uncontroversially a Lisp. However, the part of this that's relevant to the point I was actually making is that Lush uses S-expression syntax, which is less readable than, for example, Python syntax.
- stewbrew 5y agoif lush were uncontroversially a lisp, I would have used it for at least one side project. IIRC things weren't that clear (back then when I stumbled over it) when looking at it in detail, which is why I decided not to use it (but don't ask me now why exactly).