use Perl

• Keep File::Find...and (Score:1)

  by sigzero (5768)

  Why not create a wrapper module with better interface? That way you can keep it...and make it "better". Seems it isn't going away anyway.
  • Re: (Score:1)

    by chromatic (983)

    Why not create a wrapper module with better interface?

    For the same reason that Buffy Summers stakes vampires instead of giving them nice suits and $50 and sending them to charm school. Sometimes dangerous things are better off really dead.

    At some point, you have to pay off the technical debt of backwards compatibility [modernperlbooks.com], at least if you have any hope of maintaining the project.
    • Re: (Score:2)

      by drhyde (1683)

      Can you come up with an actual reason instead of a poor analogy? Unlike fictional vampires, File::Find only harms those who choose to be harmed by using it directly. File::Find is more like a big fried breakfast with all that nasty fat and EVIL meat, and we have a technical term for people who say breakfast should be banned. That term is "idiot".
      • Re:Keep File::Find...and (Score:1)

        by chromatic (983) on 2009.02.18 14:17 (#67487) Homepage Journal

        Unlike fictional vampires, File::Find only harms those who choose to be harmed by using it directly.

        ... such as Perl novices who quite logically believe "It's in the core, so it must be good!"

        Consider Matt's Script Archive. How many people cut and pasted that code without realizing that it was buggy and insecure?

        Which is easier, correcting all of the existing code and tutorials and documentation to add a disclaimer that File::Find is difficult to use and that there are better alternatives, or formally deprecating File::Find altogether in a new version of Perl?

        (Assume that Perl 5 has a regular release schedule and thus can support a formal deprecation policy.)

        Reply to This

        Parent