Perhaps I'm biased, but that hardly helps. Still far less readable than the C++ version which looks almost exactly how you would write out a math problem.
Yeah, I wanted to point it out as well, but I realized it's the text renderer that didn't format his expression correctly. If you do a copy-paste, you'll see that he indented it properly.
I did in fact copy and paste the code directly from the article into my comment above. The only reformatting I did was to add the same number of spaces to the beginning of each line in order to have HN display it as code.
If I was being pedantic about the formatting, the error would be excusable. But the code is presented as evidence that Lisp code is hard to read, so the poor formatting is highly relevant. Furthermore, when presenting C++ code earlier in the article, the formatting is correct:
typedef std::map<std::string, int>::value_type vtype;
vtype things[] = [vtype("one", 1),
vtype("two", 2),
vtype("three", 3)];
std::map<std::string, int> m3(&things[0]
Which is more readable:
The article misformats the example Lisp code [at least in two of my browsers]:
should be: