Programming means making trade offs. Ideally, code should be correct (well, that usually isn't a trade off), fast, resource friendly, small memory footprint, small amount of code, easy to maintain, easy to understand. Usually, optimizing one thing means pessimizing the others.
What is "best" depends on what your goals are. Code can be quite different whether you have the need for speed, or whether you just want clean, extensible code. And when it comes to "easy to understand", different people prefer different idioms. That's why Perl has many ways of doing things. If you prefer having a language where someone else will decide how things should be done, use Python, or to a lesser extend, Java. But even what one person prefers differs over time. For instance, because they start knowing Perl better, or are getting more experienced in programming in general. Or they are like me, I use more yellows in the morning, and gradually use less yellows and more blues in the course of the day, finishing with deep purples past midnight.
-- Abigail
In reply to Re: Is too little too much? Coding under the microscope...
by Abigail
in thread Is too little too much? Coding under the microscope...
by snafu
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |