[legooolas]

> With code, less is more, less code to do the same means easier to read, easier to maintain, less bugs.

Whilst this can be true, it's not always the case. Squashing code down to fewer lines can also mean doing something in a way that is much harder to understand or hides bugs behind complex subtleties in the code. Obviously it's a balance, and "lines of code" is, as usual, a poor metric of code complexity and readability.

[reacweb]

For me, fewer lines means that it is easier to get a whole picture. More verbosity often induces splitting code in many methods.

As always there is a balance, but I am more often annoyed by gratuitous verbosity than by cryptic constructions.