3 ms·
Ironically, this comment of yours is a great analogy to explaining this situation. I have no idea what your run-on sentence is trying to say, and don't want to
by cocktailpeanuts 10y ago
Ironically, this comment of yours is a great analogy to explaining this situation.
I have no idea what your run-on sentence is trying to say, and don't want to bother trying to figure out what you're trying to say either. And this is my point. Being too "expressive" makes it hard to share ideas. That's why they teach you to not use run-on sentences at school, but people still use them sometimes because it's easy to get carried away.
In a normal human language like English this flexibility and expressiveness is not always a bad thing since it allows all forms of art, but programing languages are not meant for avant garde navel gazing. They are for getting stuff done. And I don't want any run on sentences on my application.
- cafard 10y agoI agree that chromatic is not the best test case; he has published a lot about Perl, and his code examples are very readable. However, it is possible to right miserably bad code in a variety of languages. The Perl that one finds (for example) on CPAN is generally straightforward and understandable. One can write lucid and powerful Perl. And I have no trouble understanding any of the sentences of the parent comment. Is your complaint that the verb "indicate" falls after the clause it refers to?
- chromatic 10y agoI have no idea what your run-on sentence is trying to say, and don't want to bother trying to figure out what you're trying to say either. This may subvert your point about the effort "most programmers" put into reading code. I think it's a superficial criticism.