Every story and comment from the Hacker News API, in a layout borrowed from 2001.
A comment on Writing a simple Lisp interpreter in Rust. Parent comment
It’s very easy to write code that’s hard to read, because everything nests and composes neatly together.
But a Lisp usually also gives you a lot of tools to structure code very nicely. Such as:
- local bindings to structure code in a LTR fashion
- macros to provide syntactic sugar
- functions are very easily extracted, because everything is an expression
- closures provide context and can be composed and specialized
Points 1 and 3 can be provided as automatic refactorings by a good editor.
So code can be literally an AST dump versus very clear and expressive with a Lisp.
There are no comments on this comment yet.
It’s very easy to write code that’s hard to read, because everything nests and composes neatly together.
But a Lisp usually also gives you a lot of tools to structure code very nicely. Such as:
- local bindings to structure code in a LTR fashion
- macros to provide syntactic sugar
- functions are very easily extracted, because everything is an expression
- closures provide context and can be composed and specialized
Points 1 and 3 can be provided as automatic refactorings by a good editor.
So code can be literally an AST dump versus very clear and expressive with a Lisp.