![]() Also If I give it less than 6 GB of heap it runs insanely slowly. I find for instance that Intellij leaks memory and I frequently have to restart it once it gets to 8+ GB of usage. I have to use Intellij at my current job and I absolutely wish we could use Eclipse instead. But, at the end of the day, above all else, its the incremental compilation and everything that builds off of it. I like Eclipse's look and feel a lot better. #Intellij vs eclipse codeI've found its code formatter to be more feature rich and useful. I've found Eclipse to always be much snappier and more responsive than Intellij and to use less memory. I also love the debug perspective and how it is separated from the regular perspective. This kind of mistake I think is much harder to make in Eclipse. I helped him figure out that he actually had about 5 sub-processes running in a debugger already and they were conflicting with each other. I remember at $lastjob when I still used Eclipse and I was helping an Intellij user try to debug something. I really dislike how Intellij handles debugging and spawning sub-processes. I've also found Eclipse's FindBugs and Checkstyle plugins to work way better for me. On the other hand, the plugin I've tried in Eclipse works great. For instance, I completely gave up on Intellij's code coverage builtin plugin. I've found that there's way more plugins than in Intellij and that they work better. I've had the opposite experience with plugins in Eclipse. In this sense Eclipse encourages better coding practices by putting the warnings your face in the problems tab. In every Intellij-driven project I've seen people do not care at all about warnings and the result is a lot sloppier code, including way more code that uses raw types, code that performs unchecked generic casts, code that makes mistakes with serialization, etc. In Intellij I get so frustrated when I can't run a unit test because some entirely unrelated java file in an entirely separate module has a compiler error because I haven't refreshed my gradle project since pulling from git. This lets you do things like run your program even if there are compiler errors in your project, or, even more usefully, run a unit test. This is tremendously helpful, for instance, when I'm doing a complicated refactoring that can't be completely automated.Īnother insanely awesome feature of this compiler is that it compiles class files with errors in them. In a single window I can see all the errors and warnings in my workspace and address them. I can't find anything remotely like it in Intellij. In conjunction with automatic incremental compilation is the problems window. Intellij tries to guess errors for you, but I find that it often misses things until you run a build manually. Any and all errors show up as feedback in the IDE immediately. When considering IntelliJ vs Eclipse, keep in mind that Eclipse is well-supported and has been open-source for much longer than IDEA. ![]() As you are editing and saving, a real compiler is recompiling your code. As far as I know, Eclipse is the only Java IDE that does. This feature is an absolute game changer in productivity. ![]() The biggest reason I think Eclipse is better is because it has automatic incremental compilation built in. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |