Apart from the bad usability, it’s double the memory, double the fun. So each time you need to step out of your main project, you launch another screen. And no, multi-module Maven projects (which IDEA handles well) are not sufficient. But I’ve never been in a situation where you don’t at least occasionally need a separate project - be it an “experiments” one, a “tools” one, or whatever. Maybe there are those small companies with greenfield projects where you only need one. You can have only one project per screen.I think this makes the experience much worse. This is not a reasonable default at all, and I think the performance issues are the only reason it’s still the default. Also, a change in Maven/Gradle dependencies may introduce compilation issues that you don’t get to see. Refactoring by adding a method parameter, by changing the type of a parameter, by removing a parameter (where the IDE can’t infer which parameter is removed based on the types), or by changing return types. Well, there are dozens of cases when it does happen. I recently complained about that on Twitter, and it turns out “It’s a feature.” The rationale seems to be that if you use refactoring, that shouldn’t happen. I know I need an upgrade, but that’s not the point – not having “build on change” was a huge surprise to me the first time I tried IDEA. And turning the autobuild on makes my machine crawl. Projects are not automatically built (by default), so you can end up with compilation errors that you don’t see until you open a non-compiling file or run a build.
And you can’t compensate for those with sugarcoating. But at least some of the problems I see have to do with the more basic development workflow and experience. Of course, IDEA has many cool features like code improvement suggestions and actually working plugins for everything. Not just because of all the key combinations I’ve internalized (you can reuse those in IDEA), but because there are still things I find worse in IDEA. I’ve been using mostly Eclipse for the past 12 years, but in some cases, I did use IDEA – when I was writing Scala, when I was writing Android, and most recently – when Eclipse failed to be ready for the Java 9 release, so after half a day of trying to get it working, I just switched to IDEA until Eclipse finally gets a working Java 9 version (with Maven and the rest of the stuff).īut I will get back to Eclipse again, soon. IDEA is like the iPhone of IDEs – its users tell you that “You will feel how much better it is once you get used to it,” or “Are you STILL using Eclipse?” or “IDEA is so much better, I thought everyone has switched,” etc. Last year, they were almost equal in usage, and I have the feeling things are swaying even more towards IDEA. Over the years, I’ve observed an inevitable shift from Eclipse to IntelliJ IDEA.
0 kommentar(er)
