To the person writing the code, yes. To the next coder maintaining the code, not likely.
To the person writing the code, yes. To the next coder maintaining the code, not likely.
http://news.ycombinator.com/item?id=2240461
On another note, why do you think lisp isn't more widely used?
In a previous job I had workmates arguing for banning "nested" Python list comprehensions. And as an example of such horrible nesting he proposed something like:
some_list = [some_function(blah)
for blah in some_other_function()
if some_condition(blah)]
What this says to me is that this guy didn't get list comprehensions at all and didn't want to. Sure enough, there's no nesting whatsoever going on here. He was just scared by non-C++-like syntax.My point is: popularity, though desirable in itself, is a poor measure of anything else. Most people run away from good things for no valid reason.
(Not saying there are no valid reasons why Lisp is not more popular, only that none would really be needed. Obscurity is quite a stable default.)
In fact, a more useful question is: "why is Lisp even used as much as it is?" The current Common Lisp standard is 20 years old, and yet it supports a pretty active if small user community, which is more than can be said of most of its contemporaries.
When you see (def-ir1-transform ...) in the SBCL source, it's immediately obvious what is about to come along (at least if you know about compilers). Similarly old C code (eg: GCC) is completely incomprehensible in comparison.
Yes it is.