3 ms·
Oh you can write bad code in every language, and I regularly do. However, some languages make it far easier for you to write bad code and Perl is at the front
by sh1mmer 16y ago
Oh you can write bad code in every language, and I regularly do.
However, some languages make it far easier for you to write bad code and Perl is at the front of the pack.
In my own opinion each programmatic device should be expressed 1 way. Shorthands are not a good long term strategy, because they increase the chances of massively diversified coding styles.
- ekiru 16y agoI upvoted you because even though I disagree with what you're saying, there's nothing wrong with your having that opinion nor with your expression of it. On the other hand, I simply cannot stand to write Python because the One Way to Do It that tends to be provided is rarely the One Way I Want to Do It. It's okay that some communities and some languages say "There should be one-- and preferably only one --obvious way to do it", though. After all, if I believe "There's more than one way to do it", that applies to languages and communities, too. If a language whose community believes in only one way to do it makes you happy, use it. If you're like me and prefer having many options to express individual pieces of code however feels most appropriate for that specific situation(e.g., expressing a series of transformations on a list as either a list comprehension or a pipeline like series of feeds connecting higher-order functions), use a language that lets you do that. Neither is better for everyone. Nor is the programmer who prefers either type of language any better than the programmer who prefers the other.