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.
  • As much as I think a more a uniform style and message would be great for Perl, I also think that releasing and marketing an application that non-Perl people would find cool and useful could do as much to fix Perl's image problem as anything else.

    After using this fictional application, a user might see that it is written in Perl and think "Hey, I didn't know that Perl can do that". They might then look at the source code and think, "Hey, this isn't the same ugly Perl that I remember from the mid 90s."

    A good

    • I think you're hitting the nail on the head.

      Everything else sets the stage... but without the killer app, we can't attract the magpies.

      Then again, a killer app which attracts developers... won't be able to retain them if the support infrastructure is a maze of twisty passages all different

      We need it all. And if somebody(s) can chart a course... then perhaps we can each scratch an itch that gets us there.

      • More and more as I read through these discussions and debates, it makes me wonder how they can be resolved. I doubt all the players involved are going to start agreeing. Most projects have pretty clear leadership to resolve these kind of problems. Who's in that position for Perl?

        If it's Larry, is he going to engage these issues or is it off his radar entirely?

        • Larry is a language designer.

          He's involved with things at the level of the language "surface".

          He's said a number of times (in person, if not in print) that other people should deal with the packaging and repositories of modules.

          Same thing extends to things like the marketing and presentation of Perl to the world. This is more the sort of thing that the TPF is for.

          • I thought so, but who then? It seems there's no single person or even group who has a leadership role, which is why there's schizophrenia. I guess that's not necessarily a bad thing, but it's not exactly comforting when a bunch of the players appear to be at odds about which direction to take the project.

            C'est la vie. No matter what happens, at least the code won't go up in a poof of smoke. =)