I recently had to use Eclipse again, after 5+ years of Emacs mostly coding sessions, and boy it was tough. I kept thinking it's just one IDE, and others are better, thinking about IntelliJ. Heh.
ps: people, take a look at Emacs, it really is nice, and only needs 8MB cough
> I kept thinking it's just one IDE, and others are better, thinking about IntelliJ. Heh.
I usually don't endorse a product or service (different tools for different tasks and different people etc) but at least try out IntelliJ. I'm pretty sure there is a reason why Google decided to dump Eclipse in favor of IntelliJ as their officially supported IDE.
You may be able to crank out code faster using vi and/or emacs - but an IDE will be more advanced to tell you mistakes that could mean a world of difference. You don't know how many times I've seen people make simple mistakes writing PHP with vi that could have easily been avoided using an IDE.
My English is often cryptic, it was flattering towards IntelliJ. Since long ago they wrote very useful code either infrastructure (their caching mechanism) or UX (thorough keyboard bindings).
What kind of errors did they fail to catch ? vi/emacs rely on external checkers, I don't know what IntelliJ uses, if they have an in-house fully fledged AST analyzer or if they reuse community made ones.
> ps: people, take a look at Emacs, it really is nice, and only needs 8MB cough
As an Emacs fan, I feel obligated to, ahh, unpack this reference.
EMACS: Eight Megs And Constantly Swapping. A Humorous Expansion of the name from when eight megabytes of RAM was more than you had, bucko.
These days, I'm sure that, if you really worked at it, you could get an Emacs process to take up as much RAM as the Chrome tab you just opened to look something up on Stack Exchange.
Some times emacs has perf issues, but Eclipse overhead is really too much for me to enjoy. And the UX is miserable, all this OOP, OSGi plugins and frameworks for this leaves me meh.
ps: people, take a look at Emacs, it really is nice, and only needs 8MB cough