If you want to have some fun, compare the features that newer Python 3.x versions have, with the features Scheme has, for example Racket or Guile.
The overlap is large: Doc strings, garbage collection, list comprehensions, lambdas, dynamic vectors, a numeric tower with arbitrary long integers, rational, floating point and complex numbers, a string formatting language, “with-form” resource guards, pattern matching, Generators, Exceptions, OOP frameworks, … it is a long list.
And still, Scheme manages to be a much smaller language than Python, and Common Lisp, while really large, is tiny compared to the specification of contemporary C++.
Oh, Lisp is perfectly readable, it is merely a matter of getting used to the syntax. I have used at work at least ten different languages in thirty years, and Lisp is definitely not particularly difficult, Scheme is even easier. And what makes it easy to parse is that the syntax is small and regular. Which you can’t exactly say from C++. Even the second most complicated modern language, for which I would nominate Scala, is an order of magnitude simpler. Rust for example is more complex than Common Lisp but far, far simpler than C++.
And is respect to Python… it suffers from the same syndrome of creeping featuritis and design-by-commitee, Python picks up more and more features which very few people really use, its just not nearly as severe as C++.
I really must play with some of the modern lisps. I’m afraid most of my experience is with elisp which while it has it’s charms I wouldn’t call a general purpose lisp.
I think the most friendly modern Lisps are Clojure, and Racket, which is a superset of Scheme. Clojure is arguably the most elegant one, extremely well documented, very good for learning, and a pleasure to work with. Due to its larger start-up time and its fantastic approach to concurrency (with built-in immutable collections), It is more geared to be used in server implementations, but it has now implementations for many platforms, not only the JVM.
On the other hand, the more powerful Common Lisp implementations, like SBCL, are seriously under-hyped. One thing that is special about Common Lisp is that one can easily debug the running program. This is not possible in the same way in other languages, since exceptions usually destroy the call stack - in Common Lisp, you can handle the error at the location it is thrown, and re-start operations.
From the Schemes, I think Guile has the best debugging experience, quite similar to SBCL. It is also very well integrated with a Linux/POSIX OS, and can with little effort call system library routines in C.
Isn’t there a joke about all languages becoming half baked implementations of lisp?
If you want to have some fun, compare the features that newer Python 3.x versions have, with the features Scheme has, for example Racket or Guile.
The overlap is large: Doc strings, garbage collection, list comprehensions, lambdas, dynamic vectors, a numeric tower with arbitrary long integers, rational, floating point and complex numbers, a string formatting language, “with-form” resource guards, pattern matching, Generators, Exceptions, OOP frameworks, … it is a long list.
What is missing in Python, but Lisps do have, are JIT compilation to native code, much better speeds of compiled code, Common Lisps superb error handling with conditions and restarts, Common Lisps inheritable global variables, Common Lisps much more detailed boolean operations, and Scheme’s tail call optimization and continuations.
And still, Scheme manages to be a much smaller language than Python, and Common Lisp, while really large, is tiny compared to the specification of contemporary C++.
Python is at least readable
Oh, Lisp is perfectly readable, it is merely a matter of getting used to the syntax. I have used at work at least ten different languages in thirty years, and Lisp is definitely not particularly difficult, Scheme is even easier. And what makes it easy to parse is that the syntax is small and regular. Which you can’t exactly say from C++. Even the second most complicated modern language, for which I would nominate Scala, is an order of magnitude simpler. Rust for example is more complex than Common Lisp but far, far simpler than C++.
And is respect to Python… it suffers from the same syndrome of creeping featuritis and design-by-commitee, Python picks up more and more features which very few people really use, its just not nearly as severe as C++.
I really must play with some of the modern lisps. I’m afraid most of my experience is with elisp which while it has it’s charms I wouldn’t call a general purpose lisp.
I think the most friendly modern Lisps are Clojure, and Racket, which is a superset of Scheme. Clojure is arguably the most elegant one, extremely well documented, very good for learning, and a pleasure to work with. Due to its larger start-up time and its fantastic approach to concurrency (with built-in immutable collections), It is more geared to be used in server implementations, but it has now implementations for many platforms, not only the JVM.
On the other hand, the more powerful Common Lisp implementations, like SBCL, are seriously under-hyped. One thing that is special about Common Lisp is that one can easily debug the running program. This is not possible in the same way in other languages, since exceptions usually destroy the call stack - in Common Lisp, you can handle the error at the location it is thrown, and re-start operations.
From the Schemes, I think Guile has the best debugging experience, quite similar to SBCL. It is also very well integrated with a Linux/POSIX OS, and can with little effort call system library routines in C.