5 ms·
Eclipse seems to be a program that consumes all available memory to turn its windows grey when you type into it. I'm not sure how you think it's suitable for J
by jrockway 14y ago
Eclipse seems to be a program that consumes all available memory to turn its windows grey when you type into it. I'm not sure how you think it's suitable for Java programming.
(More seriously: Eclipse is not suited for text editing, but it is suited for dragging and dropping getters and setters. If that's what Java programming is to you, you can save a lot of time with Eclipse.)
- jsankey 14y agoEclipse is bloated, granted, but if you think its strong point is "dragging and dropping getters and setters" then you haven't seriously tried it. I used to think IDEs didn't matter much for basic code editing, but had to change my opinion after using Eclipse and IntelliJ (my preference) for a while. Higher-level (as in -- with knowledge of the programming language) editing and refactoring can make a big difference to your editing experience. Tasks that were tedious become trivial and part of the normal flow. You actually find yourself writing code in a different way once you understand how easily you can manipulate blocks of code (rather than just blocks of text).
- snprbob86 14y agoI've been stuck doing Java lately (grumble grumble). I love Vim, but occasionally, I just want an IDE to dull the Java boilerplate pain. I've been copy pasting sample snippets in to IntelliJ, auto-adding all the import statements, and then going back to do my main coding in Vim. I have to close IntelliJ quickly, however, lest the Swing fonts BURN OUT MY RETNAS on my Linux box. How can anybody get any work done with font rendering that bad?!
- Flow 14y agoJetbrains are changing their platform to use native font rendering. From their blog: "default look and feel on Linux changed from GTK+ to Alloy IDEA – it uses system fonts and has a much better overall quality (worth to try for current users too)"
- Daire 14y agoYou can get vi keybinding plugins for IntelliJ and Eclipse (and netbeans). They make it a little better.
- eta_carinae 14y ago> Eclipse seems to be a program that consumes all available memory to turn its windows grey when you type into it. I'm not sure how you think it's suitable for Java programming. Considering that about half of the Java community uses it and is quite happy with it, did it occur to you that maybe, your experience with it was not representative?
- Evbn 14y agoJrockaway works at Google, where their Java workspaces are roughly equal in total LOC to all Ruby in production everywhere.
- jrockway 14y agoThat's about right. It's true that my experience with Java is not representative, but I'm still unclear what would happen if I did manage to get Eclipse working correctly. Emacs can organize imports, complete symbols, jump to definitions, and things like that. It can't refactor as intelligently as I imagine Eclipse can, but the one time I've needed to do a really big refactor I just did it manually with a Perl one-liner (I should have written a full script, in retrospect) and cleaned up the handful of mistakes when reviewing the diffs. (That's generally how I feel about Eclipse. It will spend several hours analyzing your source code so it can do a perfect variable rename. But you can get 99.99% of the way there with "perl -pi -ne 's/int foo/int bar/g'" and fix the two cases it broke in seconds. I'd rather not write that and not do the fixup, but with so much cognitive load to make that automatic, it just isn't worth it. Why does refactoring Java require a complicated GUI application with more settings than the Space Shuttle?) The one feature I really want is something that detects what problem I'm trying to solve and shows me the documentation for libraries that can help. But really, I wish someone would write an article like "why I switched from vim to Eclipse", but I only ever see ones where the author does the opposite.
- eta_carinae 14y ago> But really, I wish someone would write an article like "why I switched from vim to Eclipse", but I only ever see ones where the author does the opposite. You haven't looked very hard, most Eclipse users today came from emacs or vi. And are you seriously arguing that a search/replace is more effective than a refactoring performed automatically with guaranteed correctness? You are being unreasonably and inexplicable biased against Eclipse (and IDE's in general), it's pretty baffling.