When your read a program it puts cognitive load on your brain. How much is a bit depended on your education and experience on the subject, but what you have to do is to transfer what you are reading to your mental model what the program is actually doing. Your capacity of things you can process in your brain is limited so you can fairly assume that the more load is put on your brain the more of that capacity is used, and the nearer your are to your maximum capacity the more difficult and exhausting is the task to understand the program.
When you need to decode a "{" or a "@" in the program to a actual processing step. you can assume that
if (a) {
b;
}
else {
c;
}
is more difficult to decode compared to IF a
THEN b
ELSE c
ENDIF.
simply the latter one is nearer to your natural language (I actually think to replace "ELSE" with "OTHERWISE" would be even better) and the "ELSE" implies both the opening and the closing braces.You can argue if
a ? b : c;
is more readable, I would argue it is not.It's not like special characters are always bad. For example
a->b
works quite well when a is pointer and the arrow "->" symbolizes graphically where a is actually pointing at. But nowadays we languages which use "->" and "=>" for different things and for their similarity they interfere which each other when doing the decoding and adding to the cognitive load.When designing a language you have to trade of brevity or number of characters to type and readability. Most, if not all languages, nowadays opt for brevity because it appeals to the developers to type less and makes it more easy have more complex functionality in one statement. The price you pay is readability and finally maintainability of the program.
I think the first programming language which failed by its overuse of badly readable syntax was Perl, which was replaced by the much more easy to read Python.
I personally believe the psychology of programming is an under-researched subject
Disclosure: Alongside to CS I studied cognitive psychology when I attended university.