4 ms·

So what about the '*' in C or even better the '.' in so many object oriented language. > The bottleneck when writing code is almost never keypresses. No, it's

So what about the '*' in C or even better the '.' in so many object oriented language. > The bottleneck when writing code is almost never keypresses. No, it's readability and that often comes with terseness. Every line break because I have to spell out lambda or every refactoring that removes the function from its original context so I can avoid a line break is bad for readability. In that aspect the '\' in Haskell does great. Also in Haskell anonymous functions are so important that they definitely deserve their own special character to shorten many expressions. I only see this becoming a problem if it is used in excess, like in C++ and especially in C++11.

jowiar 13y ago
> So what about the '*' in C I don't like it... I don't what I'd do if starting from scratch, and there might not be better, but it definitely causes readability pain. > the '.' in so many object oriented language I have less of a problem with this, because there's some non-programming analog to be found (Section 1.1, Article 3.2, etc.). That said, I think, at some point, it's harmful to OOP in that it makes it hard to sort out properties and messages, and the roles of one or the other. I agree 100% on readability - the problem for me comes when words get mapped onto abbreviations and symbols that are almost entirely constructed and/or alien to most readers.