3 ms·
The argument of "readable" code is like saying Steak taste better than Chinese food: it depends on your audience. I used to buy the whole dynamic language argu
by hello_moto 15y ago
The argument of "readable" code is like saying Steak taste better than Chinese food: it depends on your audience.
I used to buy the whole dynamic language argument (heck I even lead local Python user group) but not any more these days.
To me, Ruby is less readable than Python. To me, when reading a large code base, Java is more readable than Python. To me LISP is weird (even though I kind of like it).
Now you said "it makes sense to optimize for readability" the problem with this statement is that less code != readable code (and I don't mean to jam everything in one line a'la Perl). I find that I need to read, re-read, think, and re-think a few times just to understand what the Ruby crowds refer to short, concise, and elegant code.
Whereas in Java, albeit more terse, I can just read within seconds to know the intention of the code.
So it all depends. Hence me not buying the dynamic vs static debate.
- rbanffy 15y ago> the problem with this statement is that less code != readable code Never said that. When writing code I never go for the least possible number of symbols (if I did, I'd write traditional APL). Still, more concise code is often closer to what you want done than the details of how you'll get it done. While I find Ruby's syntax a bit confusing at times (and that's why I prefer Python) I cannot deny idiomatic Ruby is very close to intention than to implementation (to a fault).