> You're programming at the AST layer, which makes adding new semantic features (say you wanted erlang style concurrency and message passing) trivial to integrate syntactically (less trivial to implement the underlying feature).
To me, this hits the nail on the head, for all the wrong reasons. Syntax isn't the problem, implementing the feature is!
If I'm writing Lisp code, why do I want it to look like Erlang? What's wrong with it looking like Lisp? ("Erlang style concurrency and message passing" is two things, syntax and functionality. Do you want the functionality? Fine. You want the syntax too? Why?)
In fact, this is kind of what the article is about. People want the syntax "their way"; it makes it hard for others to work with their code.
The only time you should invent new syntax is when it is impossible (or very hard) to say something in the syntax you've got. "I don't like it" isn't good enough. "It will save me a few keystrokes" isn't good enough.
To me, this hits the nail on the head, for all the wrong reasons. Syntax isn't the problem, implementing the feature is!
If I'm writing Lisp code, why do I want it to look like Erlang? What's wrong with it looking like Lisp? ("Erlang style concurrency and message passing" is two things, syntax and functionality. Do you want the functionality? Fine. You want the syntax too? Why?)
In fact, this is kind of what the article is about. People want the syntax "their way"; it makes it hard for others to work with their code.
The only time you should invent new syntax is when it is impossible (or very hard) to say something in the syntax you've got. "I don't like it" isn't good enough. "It will save me a few keystrokes" isn't good enough.