3 ms·
The second example is vastly more readable in terms of understanding what it is supposed to do. I mention this as neither a programmer on either Scala nor Go.
by nunobrito 10y ago
The second example is vastly more readable in terms of understanding what it is supposed to do.
I mention this as neither a programmer on either Scala nor Go.
If it is of any relevance, I've been writing code for about 20 years across C, Java, Javascript, PHP and shell scripts. I'm sure other FP developers will roll their eyes to a traditional developer like me but the one-liner you mention is simply not self-explanatory for an outsider when reading it.
- spdionis 10y ago"I've been speaking italian, french and spanish for 20 years. I'm sure people who speak germanic languages will roll their eyes to a traditional latin-languages guy like me, but the german sentence you mention is simply not self-explanatory for an outsider when reading it."
- kaoD 10y agoThe second one is so readable it contains a subtle bug nobody noticed.
- sacheendra 10y agoBut that would be caught by the compiler. The error would be variable not defined.
- deleted 10y ago[deleted]
- gribbly 10y agoWhat 'subtle' bug ? It returns 'email' instead of 'emails' which I assume was a typo, which of course the compiler would complain about, are you claiming that a variable name typo is somehow a 'subtle bug' ? Only other thing I see directly is that 'users' is undefined, but this is a code snippet after all, not a working program.
- kornish 10y agoI think kaoD's point is that more code will always produce more errors, and more code (in the name of "readability") can give more surface area for bugs.
- matt_kantor 10y agoOut of curiosity, what specifically do you find unreadable about the first example?