Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • Regardless of the problems with TIOBE, I think there is at least something of a downwards trend in Perl in certain envrionments.

    There are a few reasons... not being able to find good Perl programmers is one reason given by my company. Also, wanting to standardise on languages as much as possible, especially for new stuff (where Java wins most of the time).

    While I think the Perl community is one of our strengths, it's also a weakness. As you say, there are some people who refuse to acknowledge what's going o

    • To be honest I think the biggest major difference in perl vs java is not lack of an IDE (komodo is nice) but the fact that a mediocre programmer can generally write relatively clean, readable and maintainable java code. Why ? It forces good practices on you. Perl OTOH not only gives you enough rope to hang yourself, it ties it into a noose before handing it over. It takes someone with godlike levels of self control not to (even occasionally) take advantage of the many shortcuts around good programming prac
      • by TheNomad (7014) on 2008.12.04 7:14 (#66192) Journal

        The argument that Perl's problem is that it allows too much flexibility is very common. But there has always been something wrong about it.

        Surely, any decent programmer is going to want more flexibility. The more things a language can do the better, surely? Even if you don't use some features 90% of the time, the fact that they can be used 10% of the time can only be a good thing.

        The problems that perl has at the moment seem mostly with mindset. Firstly of marketing - there is not one big high profile project at the moment that people say is perl. Catalyst doesn't have the profile of Rails. And nothing seems to have the profile of WordPress or Drupal.

        Secondly, there's a bit of an Osborne effect with Perl6. I'm always thinking whether my code will run on Perl6 and what changes I'd have to make? What are the 20% edge cases that are going drain 80% of my time? How can I write perl 5 code that will make it easier for the converting parser? Will key packages like and work on perl6? The community needs to address this somehow. Sorry I don't have a solution just right now.

        Thirdly, the backwards compatibility issues on CPAN that chromatic talks about need to be addressed. Simply put, module maintainers need to make the decision to break some old code. I guess I'm influenced by some XP practices which suggest that if you need to break old code, break it, but give people an upgrade path.

        I guess all of these problems can be solved.