3 ms·
Thank you zimbatm! These are great comments. Your point is a great one. I could write a program in bash with 2 words that might take dozens of nodes in Python:
by breck 9y ago
Thank you zimbatm! These are great comments.
Your point is a great one. I could write a program in bash with 2 words that might take dozens of nodes in Python:
wget https://news.ycombinator.com/
But in reality what's happening is just the complexity is shifted from the user to the interpreter creator.
LISP programmers are used to this. ETNs are very much like Lisp, except it removes the AST parse step (and the parentheses!), leaving the resulting programs simpler than their Lisp equivalents.
- kazinator 9y ago> ETNs are very much like Lisp, except it removes the AST parse step (and the parentheses!), leaving the resulting programs simpler than their Lisp equivalents I don't see how this is different from: Sweet Expressions: - https://www.dwheeler.com/readable/ https://www.dwheeler.com/readable/ Wisp: - http://dustycloud.org/blog/wisp-lisp-alternative/ http://dustycloud.org/blog/wisp-lisp-alternative/ and some others.
- deleted 9y ago[deleted]
- kazinator 9y agohttps://srfi.schemers.org/srfi-49/srfi-49.html https://srfi.schemers.org/srfi-49/srfi-49.html