Running Lisp in Production (2015)

Re:Running Lisp in Production (2015) by TeMPOraL on Sunday May 24, 2020 @05:53PM (#23295182)

"Unreadable" is a choice at this point.

Here's a simple trick to make Lisp instantly readable. Take a line of code from an algol-like language:

  foo(bar(), baz(quux))

then, shift every opening parenthesis one token to the left:

  (foo (bar), (baz quux))

and drop the commas:

  (foo (bar) (baz quux))

Now you have an equivalent piece of Lisp code.

[ Parent | on HN ]

Re:Running Lisp in Production (2015) by klyrs on Sunday May 24, 2020 @09:23PM (#23296743)

Hard agree. I don't use lisp, but people in an adjacent department do (yes, in prod). It takes a few minutes to learn to read lisp. Arithmetic takes a lil bit to grok, but short expressions are easy. I wouldn't share lisp that I've written with my coworkers ;)

[ Parent | on HN ]

Re:Running Lisp in Production (2015) by dwheeler on Monday May 25, 2020 @01:18AM (#23298094)

If you prefer to use Lisp with a more conventional syntax, check out "readable Lisp: https://readable.sourceforge.io/

It has three levels of notation, depending on what you want. There is even a quick lisp library.

[ Parent | on HN ]

Re:Running Lisp in Production (2015) by TeMPOraL on Monday May 25, 2020 @04:15AM (#23299121)

Personally, I like Lisp the way it is. I fully agree with this image:

https://www.reddit.com/r/lisp/comments/e2e5o/lispovision/

[ Parent | on HN ]