Then when you add in other little features that you can do in emacs, like fading the parens close to background colour when you're not working on them, highlighting when you are, etc... It all adds up to make the old "parenthesis hell" a bit nonsense.
I sometimes imagine that there must've been a stage when universities forced people to write Lisp in Notepad or something, or by hand maybe. I can't imagine how much that would drive me insane!
The problem is that many programmers and academics today are unwilling to take the time to learn the right tools for the job.
In fact (if you didn't know) lisp M-expressions using whitespace and indentation existed long before python (though the original M-expression syntax idea was based on FORTRAN). The reason M-expressions aren't used in place of S-expressions is because people using lisp preferred and continue to prefer S-expressions.
Of course, this is a terrible idea and very un-lispy, because one of the key benefits of lisp is that it's simple to parse. Introducing infix operators destroys that simplicity.
Another workaround, which I quite like, is to simply remove all the "lisp syntax" entirely, and edit a tree directly using a syntax directed editor.
()
prin1
()
*
()
+
3
4
7
Exceedingly vertical, obviously, if you don't allow inline parens at all.If you were, you could compress any run of lines by simply moving everything with no children into the parent parens. Applying that only to the deepest bit of the above, we'd get:
()
prin1
()
*
(+ 3 4)
7
Of course, the original could be transformed into actual lisp by simply moving end-parens: (
prin1
(
*
(
+
3
4
)
7
)
)Ur-Scheme: http://canonical.org/~kragen/sw/urscheme/
An Incremental Approach to Compiler Construction: http://scheme2006.cs.uchicago.edu/11-ghuloum.pdf
PicoLisp: http://picolisp.com/5000/!wiki?home
Lambda-the-Ultimate papers: http://library.readscheme.org/page1.html
SICP: http://mitpress.mit.edu/sicp/full-text/book/book.html
LiSP: http://www.amazon.com/Lisp-Small-Pieces-Christian-Queinnec/d...
Maru: http://piumarta.com/software/maru/
Edit: You might also enjoy Jonesforth (see jonesforth.S): http://git.annexia.org/?p=jonesforth.git;a=tree
Java, for example, is completely awful to write (I find) without the use of Eclipse or some similar tool. C and Ruby, by contrast, I'm happy to hack on in Vim.
Well, it has all of _three_ types of brackets, which may be reassuring to the C++ programmer.
Having syntax for 4 different data structures instead of just one would be one of my main reasons. Also, the syntax of a lisp-1 is cleaner.
I guess, syntax-wise, the main difference is no longer needing funcall, which was a headache when I was learning CL.
The Lisp-2 design has a very good practical reason: 50% of a common type of mistake are impossible to make. More namespaces don't hurt a language, while less namespaces usually do (Javascript for instance).
I don't buy it. Nobody wants to talk about these apparently obvious (to non Lispers) problems of Lisp, yet they are still there? Bring them up and be argued with or be quiet.
Later he talks about the ugliness of Lisp syntax, especially CL, but Scheme and Clojure are supposed to be better. On what basis? I may admit scheme is elegant, but calling clojure's syntax an improvement over CL is a pretty long jump.