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.
  • I like Eric Raymond, probably more than anyone else here, but nothing I've seen about this book has given me a compelling reason to read it, or even a minor reason to read it. I read some of the earlier online samples and picked up nothing.

    There's only so many ways to say, "small tools with clear defined purposes."

    There are so many other books out there that can affect my programming in profound ways. I still gain much from a simple reading of the Mythical Man Month every year.

    J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
    • There seem to be two large groups of writers. One writes with confidence, believing that they know their material. The other writes anyway, hoping that no one who really knows the material will come along later and say "That's completely wrong."

      There's also a much, much smaller third class: those who really do know the material and don't suffer from imposter syndrome. Fortunate them.

  • I read through some of it too. Agree on all points. However, there is a need for a text kind of like this. I used unix for a year before I understood the idea of small tools -- Unix Power Tools [] was my key to enlightenment, and only in an inductive way.

    One saving grace: ESR came close to saying something interesting about vi versus emacs []. I found the discussion of the Plan-9-inspired wily [] particularly illuminating.

    Unfortunately, because he's ESR, his interesting start ended with him bullying the facts in

  • I'm just waiting for people to use ESR's personal preferences (Python over Perl, emacs over vi, etc) to push their own agenda at companies. "We're standardizing on Python, because Perl is a nasty, write-only, line-noise language. See, ESR said so, and he's a Recognized Figure."

    I like much of his stuff, and I know that those waging holy war over languages and editors don't really need his blessing, but think about explaining to a PHB why you're right and this International Man of Definitions [] is wrong.