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.

Windows Patches Welcome; Windows Attitude Not 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • As a Windows (and Solaris) developer, I'm afraid I feel his frustration. Look, I realize this is all free stuff, and noboby owes anybody anything, yada, yada.

    But, after you've submitted your 427th patch to make yet another library Windows compatible because yet another Linux dev decided to shell out with a 'grep' command it seriously starts to grind you down over the years.

    It's not just Unix bigotry. I've noticed a serious trend towards Linux bigotry (or rather, the GNU toolchain), as I've run into my s

    • It's not just Unix bigotry. I've noticed a serious trend towards Linux bigotry (or rather, the GNU toolchain), as I've run into my share of problems with libraries that wouldn't build properly on Solaris, too.

      I agree, having tried to write cross-platform C code (which is an order of magnitude more difficult than cross-platform Perl, Python, or Ruby code). Of course, it doesn't help that the default Solaris compiler is apparently dumber than most forms of rocks. (Not Shale. Shale is particularly dumb.)

      What I would like is for developers to think in advance about writing cross platform code instead of just, "Oh, I'll just toss this out there and wait for the patches", which is how it often feels.

      Mostly that attitude seems to come from fixing lots of broken code, whether their own code or code they want to work on their own platforms.

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.