Le jeudi 26 janvier 2006 à 20:04 -0500, David Nusinow a écrit : > On the other hand, adding languages only adds to the complexity and tools > that a Debian developer should know to be effective.
Despite the days of nightmare I have spent on perl, I couldn't claim to be "effective" with perl. When I have an issue with a perl script in Debian, I call for help from another developer. When there are hundreds of developers, you can always find one with the skills and some time to help. This is true the other way round: there are now enough developers skilled with python, so that a developer with a python issue can call for help. > I've learned large > chunks of my bash and perl knowledge to reduce this problem in my own work, > rather than write it in the language I would have chosen had I been first > to the site. While perl has its share of problems, it's not that bad and > refusing to work in it is a little absurd. Perl is a completely absurd and counter-intuitive language. When you're used to clear and strict types, you have to wonder how that dumb software will interpret it and what will happen at each line of code. Writing code in perl is a pain that takes me 10 times longer than writing it in python - for the things I manage to write. I'm not event thinking about understanding most perl scripts out there: the TIMTOWTDI philosophy leads to as many kinds of programming as there are perl programmers. In other words: you cannot only learn perl, you have to think in perl. Which is a very hard task for people used to structured languages. -- .''`. Josselin Mouette /\./\ : :' : [EMAIL PROTECTED] `. `' [EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom
