I have used the Active State PDK in the past. I rather liked it as a developement tool. The integration of the debugger was a nice bit; I like having multiple windows open in the code and the debugger, so the ActiveState methodology fit right in. At the time I thought that it was a worth while investment.

The down side I found was that modules hit CPAN several days (or in hard cases weeks) before they were available from the PPM repository. But that's a bad thing only if you have to be at the (b)leading edge; for the more cautions of us, it should not cause problems.

Lately I have been doing most of my coding on Linux/Solaris and "porting" over to Windows during the last week or so before a code release. It does require a little pre-planning to keep the module libraries in sync. You can't just add a new version of something without verifying that the module is available in both environments. Like a lot of other things, it's just a matter of a little prior planning.

If I were developing in a pure Windows environment again, I'd upgrade my PDK. But I'd also look at pEdit and at Eclipse as well. (My current IDE is called 'vim'.)

----
I Go Back to Sleep, Now.

OGB

In reply to Re: Perl Dev Kit - opinions sought by Old_Gray_Bear
in thread Perl Dev Kit - opinions sought by crabbdean

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.