While I agree whith the "whatever works for you" philosophy, it's probably worth asking him if he wants an IDE just because that's what he's used to.

If he's never tried living inside emacs (my favourite) or vim + shell it might be worth his while trying it out. If someone can use a "project search" function of an IDE but has never learned to use grep is going to miss out when he tries to grep log files etc.

OTOH, if you are always a vim + shell person it may be worth *your* while trying out a more interactive environment. I especially love the interaction between emacs and the perl debugger - I assume the EPIC or ActivePerl debuggers would be even better.

In reply to Re: Professional Toolkits <=> vim + shell by aufflick
in thread Professional Toolkits <=> vim + shell by codeacrobat

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.