Here's what I think is a good IDE:
- It doesn't get in the way of an experienced user. Or, more strongly, it's aimed at the experienced user. Remember, you're only a newbie for a short time, and experienced for a lot longer.
- It works right out of the box. Even without your personal configuration file, it should feel "home". Little configuration should be needed in general.
- It should be there when the OS is freshly installed, for any OS I work with.
- It should come with a manual page. Manual pages are written in *roff. Not in infodoc. Not in HTML. Not in XML.
- It shouldn't be geared towards a specific language. It should be equally usable whether I write Perl, C, LaTeX, SQL, an email or a plain text file. I don't want different IDEs for every task I work on.
- It should run on any console or terminal that's capable of cursor movement.
- It should be fast enough that it can work over a network.
Luckely, vi and its lookalikes have been doing that for me for about 30 years.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
