{"id":2288,"date":"2011-03-03T19:21:15","date_gmt":"2011-03-03T19:21:15","guid":{"rendered":"http:\/\/t.motd.kr\/articles\/2288\/what-i-don-t-like-about-intellij-idea"},"modified":"2022-12-28T01:44:43","modified_gmt":"2022-12-27T16:44:43","slug":"what-i-dont-like-about-intellij-idea","status":"publish","type":"post","link":"https:\/\/vault.motd.kr\/wordpress\/posts\/2288\/what-i-dont-like-about-intellij-idea\/","title":{"rendered":"What I don't like about IntelliJ IDEA"},"content":{"rendered":"\n
Although IntelliJ IDEA<\/span><\/a> is a very nice IDE<\/span>, I hate several things about it, especially comparing to Eclipse<\/a>.<\/p>\n Not IDEA<\/span>’s fault, but its font rendering in Linux is horrible. Everyone who recommends IDEA<\/span> seriously was Mac user, and that might mean something is wrong with Swing. Fortunately, I found a workaround<\/a>.<\/p>\n The default keymap is not easy to learn & remember. How can I know if Ctrl+F9 means ‘Make project’ and Shift+F6 means ‘Rename’? Ctrl+B and Alt+Shift+R of Eclipse are much easier to remember. I know we can’t do it that way for all shortcuts, but at least we should do the best. Some old IDE<\/span>s had the similar keymap with IDEA<\/span>, and in my opinion IDEA<\/span> looks like it simply followed some bad tradition.<\/p>\n The default color scheme (i.e. syntax coloring) looks so 80-ish. It makes me feel like working with a very old IDE<\/span> such as Visual Studio 6.0. Most modern text editors like TextMate<\/a> and Sublime Text<\/a> have much more lovely out-of-the-box color schemes.<\/p>\n Personally, I prefer the color scheme of Eclipse, and use the same color scheme in IDEA<\/span>. If you like Eclipse style, download it here<\/a>.<\/p>\n There is a plugin called ‘Eclipse Mode’ that emulates this behavior, but it is not in the same league with the native incremental compilation engine that Eclipse ships with, and it doesn’t seem to work with the latest IDEA<\/span> version.<\/p>\n Eclipse has a view called ‘Problems’ which shows all errors, warnings, TODO<\/span> tags of the project (or the scope you prefer). In combination with the ‘build on save’, the Problems view updates the list of problems almost in real time. In contrast, I have to build the project manually to get or update the list of warnings and errors.<\/p>\n I have to type CTRL<\/span>+Q to look up the Javadoc of a class on the current cursor position. Why can’t I simply view the Javadoc by moving my mouse cursor on it instead of moving the text cursor? It does seem like some people doesn’t care about this lack of feature, but without this feature I have to move the text cursor back and forth in the middle of coding session instead of briefly moving the mouse cursor while retaining the current text cursor position.<\/p>\n Also, did you know most applications define CTRL<\/span>+Q as a shortcut for ‘Quit’?<\/p>\n","protected":false},"excerpt":{"rendered":" Although IntelliJ IDEA is a very nice IDE, I hate several things about it, especially comparing to Eclipse. Horrible font rendering Not IDEA’s fault, but its font rendering in Linux is horrible. Everyone who recommends IDEA seriously was Mac user, and that might mean something is wrong with Swing. Fortunately, I found a workaround. Meaningless… Continue reading Horrible font rendering<\/h2>\n
Meaningless keymap<\/h2>\n
Unstylish color scheme<\/h2>\n
No ‘build on save’<\/h2>\n
No way to browse the complete list of errors and warnings of a project<\/h2>\n
No quick documentation lookup on hover<\/h2>\n