Seven Low-Cost Ways to Improve Legacy Code
Subject:   IntelliJ IDEA
Date:   2004-04-29 16:25:40
From:   Robert Simmons Jr. (Kraythe)
Response to: IntelliJ IDEA

Since I have never used IntelliJ, I will take your word for it. =) However, Eclipse can do these things as well, especially the new M8 version; and for a lower cost.

However, whichever tool you use, make sure to turn on thos options and use the tools available! =)

Full Threads Newest First

Showing messages 1 through 2 of 2.

  • IntelliJ IDEA
    2004-04-29 18:20:38  michaelcherichetti [View]

    You should try it, you'll never utter the word Eclipse again if you do, take my word for it :) The only reason I suggested IntelliJ was that you said in #3 that you didn't know of any tools that could automate the process and also said that Eclipse couldn't do it, so can it do it or not?

    Anyway, I agree that the tool doesn't matter as long as it gets the job done, but please don't do yourself the injustice of ruling a tool out just because it costs money. In my opinion, IntelliJ is a *steal* at $499.

    By the way, I love your book. I am a long user of final to prevent logic errors. When someone argues with me nowadays about it I direct them to your book, so thanks for that chapter :)
    • IntelliJ IDEA
      2004-05-01 15:12:17  mikeunicode [View]

      - I'd like you to give us some clue about how to Set up Eclipse to do this code checking, and publish that as a major article on OnJava.
      I've run into problems attempting to use open source projects( developed with using Eclipse ) with JDeveloper catching errors in the libraries, making them unusable.

      - What version of JBuilder are you denigrating?
      JBuilder X catches more bugs than I care for actually.

      I'm not a big fan of Eclipse.
      Using SWT breaks the Pure Java mantra.
      Is this IBM's smart move to turn Java into a fragmented Unix environment. IBM can then have a Big piece of a much smaller pie.