Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

So I am not alone. I too have been using the vi/command-line development suite for as long as I can remember. There are a few reasons for my use of vi/command-line development (and not just for Perl).

First, is just as you said, there is a necessary time period needed to familiarize yourself with a new programming environemnt. With my current development habits, I can go from language to language with no need to spend time on learning the interface. In my opinion, this also lets me focus more on the code that I'm writing and not on looking for the "Compile" button.

Secondly, it helps when working on older systems. I know that everyone has got an old clunker that they have to work on at some point as part of their job, and an IDE would floor the system. The combination of vi/command-line lets me get my work done and not kill the system in the process.

Another reason that I have shied away from IDE's is horrible error messages. I have found that some suites simplify/group errors into generic messages that often make debugging difficult. For example, Borland started using the "Error: Thread stopped." (or something to that effect) a little too much to be useful. You'd get that error if you overstepped memory bounds, used the incorrect type, or even if the server handing out the headers was being stubborn.

I personally don't see myself changing how I develop in the near future. I plan to keep on using vi as my development suite for years to come.


If the world is to end in a whisper, I hope that it's not someone whispering,"I wonder what this button does?" -DTB

In reply to Re: Perl Programming Tools - (who, what, where, when, and why) by haxordan
in thread Perl Programming Tools - (who, what, where, when, and why) by diakonos

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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others having an uproarious good time at the Monastery: (5)
    As of 2021-04-11 22:48 GMT
    Find Nodes?
      Voting Booth?

      No recent polls found