Originally posted by Dmitry Jemerov:
Indeed, Eclipse is a platform, which has upsides and downsides for Java developers working in Eclipse. Indeed, there are many other products that are built on the Eclipse platform. But this also means that Eclipse JDT is just one of many tools running on the platform, and the needs of the Java support are not always top priority for the platform developers. On the other hand, IntelliJ IDEA focuses on being a Java IDE, and we try to provide the absolutely best Java development experience with no compromises.
We do not have any plans to make IntelliJ IDEA a platform. This doesn't make business sense for us and won't help the users either - all the companies which have already invested in the Eclipse RCP won't suddenly switch simply because another platform became available.
Also, it is not feasible for us to support Eclipse plugins in IntelliJ IDEA. The architecture is simply too different - we would have to spend lots and lots of work reimplementing the Eclipse APIs over our own codebase.
Originally posted by Dylan Honorez:
I would use IntelliJ for coding, Eclipse for Integration with business logic and finally NetBeans for making GUI's (which I think is something IntelliJ needs to review urgently).
Originally posted by Tim Holloway:
If you think you can't do GUI's in IntelliJ, you probably haven't tried IntelliJ 6. While it lacks a a WYSWIG JSF editor, it does great Swing design.
Now I no longer have to use my antique copy of Visual Cafe to layout Swing apps!