The only downsides I've found are:

(1) it's more of a pain to try out modules that may or may not be PowerPC friendly, since so much code out there is developed on x86 architecture. CPAN works but doesn't manage package installations and dependencies like Fink would, and Fink rarely lists the perl package you want.

(2) you can't use generic shebang scripts as Speakable Items and probably some other carryovers from pre-OSX days. You have to wrap each one with a little AppleScript stub instead. There are easy programs to make those stubs, like Platypus.

I haven't tried Gtk2::* packages on OSX though. If someone else lets me know how that works out, I'd like to know.

--
[ e d @ h a l l e y . c c ]

In reply to Re: Where does Perl fit into OS X? by halley
in thread Where does Perl fit into OS X? by Acolyte

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.