so being a Mac OS X user, I had always written my code in either XCode or
SubEthaEdit. However, there was a group Java project I was working on and they
tried to convince me to use Eclipse.
The good: it immediately shows when you have errors in your code, such as
undefined types (when you're missing an include), missing semicolons, etc, etc,
without requiring you to recompile. You can also run JUnit tests.
The bad: it is unbelievably slow on my PowerBook G4 867. In addition, it
seems to have some strange caching policy for files, so that if you modify a
file outside its environment, you have to "Refresh" your workspace for
it to notice it. What the hell? When I modify a file in Eclipse, the changes
show up in XCode immediately!
Verdict: too slow to use on my machine and has some really strange quirks.
Next time, I'll try to get a solution that wouldn't require running it to do my
work (i.e. run unit tests).
Review by lensovet (about 1 year ago)
so being a Mac OS X user, I had always written my code in either XCode or SubEthaEdit. However, there was a group Java project I was working on and they tried to convince me to use Eclipse.
The good: it immediately shows when you have errors in your code, such as undefined types (when you're missing an include), missing semicolons, etc, etc, without requiring you to recompile. You can also run JUnit tests.
The bad: it is unbelievably slow on my PowerBook G4 867. In addition, it seems to have some strange caching policy for files, so that if you modify a file outside its environment, you have to "Refresh" your workspace for it to notice it. What the hell? When I modify a file in Eclipse, the changes show up in XCode immediately!
Verdict: too slow to use on my machine and has some really strange quirks. Next time, I'll try to get a solution that wouldn't require running it to do my work (i.e. run unit tests).