Stories
Slash Boxes
Comments
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.
 Full
 Abbreviated
 Hidden
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 Lecar_red (5694) on 2008.12.04 16:19 (#66240) Journal

        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.

        I think the perception that this is true is the problem. And I don't know how to fix that. I have read lots (lots, lots, lots) of really poorly written Java code created with various IDEs. The IDEs allow people to discover language features that are hidden or require some research, but since they've been found it doesn't mean they understands how to use the feature (or use it properly without later bugs). I'm sure this is not a good thing for maintainabilty. I'm conflicted about tools, esp. ones that generate or help generate code. They seem to create lots of code that doesn't often quite work or later is maintainable (since they include confusing variable names and such). The big advantage of IDEs, as the poor maintainer later, is the support to easiy look up variable declarations and definitions.

        As for your other points, I would agree that PHP has picked up many young and startup web coders. I think that is many due to it saturation in the web hosting space and its native-ish database integration. Also, for beginners its pretty easy to have a web template (from somewhere else), add php code then run through a web server and have a quick app/site. I think its pretty slick that it can be that quick. Also, its simple there aren't 10 choices for templating languages (well there are but not right away) or half dozen web app frameworks. I like the choice but not when I'm trying to figure out something for the first couple of times. In the beginning its just a lot of frustrating noise thats in my way.