I use Visual Studio heavily at work and Komodo somewhat, which reflects the balance between the amount of C++ and the amount of Perl I develop. In most ways Komodo is at least as good as an integrated debugger as VS - better than VS2009 in fact where MS have broken fundamental stuff such as breakpoints!

For the stuff I do at work and where the productivity boost justifies the cost the price of the pro version is not a disincentive. For the Perl programming that I do at home, for which there is no remuneration and the productivity boost is less relevant, the cost of the pro version of Komodo is a complete blocker. The 'personal edition' that was available for Komodo 3.x was great for a my home use and I was responsible for the purchase of three copies - 2 x pro for work and personal for home.

Stability is a good reason to upgrade actually. 5.1 is much more stable, especially during debugging, than 3.x was. It was exactly that issues that drove me to upgrading at work. Actually, now I think about it, it was 3.x I was using. Komodo changed their price structure going to 4 and pissed me off to the extent I held off until well into the 5.x life cycle before upgrading.

True laziness is hard work

In reply to Re^3: Komodo 5.1 versus the others. by GrandFather
in thread Komodo 5.1 versus the others. by Steve_BZ

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.