comment on

I have used a ton of IDE's, and currently use Visual SlickEdit in vi emulation mode... or just plain vi when feeling lazy (ok, mostly just vi).

When it comes to the ever present goal of witting code faster, and more consistent, i have found that it is not as much the IDE, as it is the code architecture. -- oops, i said one of the scary words. If you make smart choices in your code architecture, like making modules where it counts, and actually thinking about loose coupling, you could write code in notepad and still be more productive than within an IDE with bad choices. This is like optimizing code with a bad choice of algorithm ... it may go faster, but not as fast as a good choice from the beginning.

just my €0.02

update: format fix. changed <br> to <p>

from the frivolous to the serious

In reply to Re: Activestate Perl and the Komodo IDE by MZSanford
in thread Activestate Perl and the Komodo IDE by monkfish

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.


"be consistent"
	PerlMonks