Every story and comment from the Hacker News API, in a layout borrowed from 2001.
A comment on Just what does “code as data” mean anyway? (2014). Parent comment
It's wrong, Lisp has a lot of syntax.
> What Lisp has, and is, is a syntax to describe an AST.
That's wrong, too. Lisp syntax does not describe an AST.
> To me, it's a chain of 5 functions which are neither shorter to write nor better than Java's jOOQ [1]:
That's not the point, the Lisp version is on another level:
* it does not expose its implementation
* the macro allows to translate this code at something like compile time
The Java code is a bunch of function invocations which create a string. Usually at runtime.
There are no comments on this comment yet.
It's wrong, Lisp has a lot of syntax.
> What Lisp has, and is, is a syntax to describe an AST.
That's wrong, too. Lisp syntax does not describe an AST.
> To me, it's a chain of 5 functions which are neither shorter to write nor better than Java's jOOQ [1]:
That's not the point, the Lisp version is on another level:
* it does not expose its implementation
* the macro allows to translate this code at something like compile time
The Java code is a bunch of function invocations which create a string. Usually at runtime.