Anyway, Walter Bright, designer of D language, wrote an article on language design [1] touching on the issue:
> Yes, the grammar should be redundant. You've all heard people say that statement terminating ; are not necessary because the compiler can figure it out. That's true — but such non-redundancy makes for incomprehensible error messages. Consider a syntax with no redundancy: Any random sequence of characters would then be a valid program. No error messages are even possible. A good syntax needs redundancy in order to diagnose errors and give good error messages.
I thought that was interesting. It is a pretty much undebatable argument against taking terseness too far.
On the other hand, I have never had a problem with Python's error messages.
[1] http://www.drdobbs.com/architecture-and-design/so-you-want-t...
"The syntax is terse" doesn't help if the libraries aren't. We want libraries and common concepts to be terse. That's why I feel that any language designed without heavy consideration for how it's standard libraries are to be used is a regressive exercise. Write your libraries how you want them to be used, then figure out the syntax from that.
Syntax matters, but not in the way most people think it does. Syntax should be judged based on how well it supports semantics of a given language and not based on how "pretty" it is. EDIT: I should probably add that Python syntax matches its semantics and intended usage rather well; for an example of a conflict between syntax and semantics look at JavaScript.
Why do you need braces when the program's tree structure is obvious from indentation?
Yes, I think so too.
> Why do you need braces
You don't. You need some kind of delimiters and newline+indent works just as well as any other kind of delimiter, like braces, parens, begin+end and so on and on.
- I find myself fighting my editor's indentation a lot more as a result. Hitting return at the start of a line in the middle of an existing chunk of code indents to the previous line's indentation not the current line's indentation.
- It's asymmetrical: code drifts off to the right as you go down. Together with the editor issue I've taken to inserting a single '#' at points of down-indentation to mark this.
I have a conditional block. I want to paste some code at the end of it. Do I want to paste it inside the condition, so indented the same as the preceding line - or outside the condition,so indented one level less than the preceding line?
With a brace delimited language, if I put the cursor inside or outside the brace and paste, an editor has enough information to correctly indent it. With whitespace delimiting, the editor doesn't have enough information.