Article:  |
A Look at the Eclipse IDE | |
| Subject: | Eclipse = half IDEA for free | |
| Date: | 2003-11-15 20:08:20 | |
| From: | anonymous2 | |
|
What is good in Eclipse, was already present in IDEA, and the implementation in IDEA is still much better. The only difference I can see is that Eclipse is free for the developer. This is not such a good news, because all the hype towards Eclipse and the funding behind it could definitely kill IDEA and leave us with a much worse product, even if sold as free. Maybe IBM should have given his money to JetBrains instead of OTI. And by the way I agree that no-one really needs SWT, especially on Mac OS X, where the Swing implementation is very good ans SWT is not. Maybe this is the reason why I cannot see any other SWT applications other than Eclipse. If OTI cannot develop in an object-oriented way, instead of producing a procedural GUI API, which obviously can be mapped to Carbon not Cocoa, maybe the should have stayed away from Java and choose a different language. And most of all I cannot stand an IDE whose behaviour gets unpredictable when the number of classes is greater than 100. |
||
Showing messages 1 through 4 of 4.
-
Eclipse = half IDEA for free
2003-11-16 19:18:11 anonymous2 [Reply | View]
-
Eclipse = half IDEA for free
2003-11-19 01:56:15 anonymous2 [Reply | View]
I'm currently using Eclipse on a project with over 400 classes and over 150 JSPs and there's nothing unpredictable about it.
Once in a while writing a file to disk takes longer than normal, but that's due to the fileserver and not Eclipse (it happens also when using other applications).
-
Eclipse = half IDEA for free
2003-11-17 16:45:27 anonymous2 [Reply | View]
My experience is using Eclipse 3.0 M4 on Mac OS X on a project using 100 classes split in 4 different source directories within a complex, not modifiable, directory structure with lots of non-java files.
With automatic compilation on, which is something that, if turned off, makes Eclipse almost useless to me, the task list updates sometimes stop, the code completion stops working or it takes too much time. Most of all there is no half-decent XML/JSP editor and because of SWT it's not possible to integrate something working, like for example the jEdit plugins, within Eclipse in a useful way.
I think Eclipse would be much better on Swing and with a less windows-like pre-XP GUI so cluttered with icons.
And way too many times the workbench configuration file gets corrupted...
What are you talking about. We have assumed maintenance of an admittedly bloated project that has over two thousand classes, and we are using WSAD (which is basically Eclipse++). There are no problems with the IDE handling the class size that I can discern.