![]() ![]() “Find usage” I think predates the call hierarchy, and is also much more visible through the UI, so some of the IDEA users don’t even know what a call hierarchy is. Also, from what I’ve seen IDEA users don’t often use the call hierarchy feature. It doesn’t give you the call hierarchy of default constructors that are not explicitly defined. But since that’s the most important IDE feature for me (alongside refactoring), it matters. Eclipse displays warnings better, and the false positives are much less. There isn’t a “yellow” indicator on the class either, so you don’t actually see the amount of warnings you have. What’s the problem with those warnings? That warnings are devalued. Even getters and setters on POJOs get the unused warnings. Maybe some spring plugin would take care of that, but spring is not the only framework that uses reflection. It uses spring, so these methods and fields are controller methods and autowired fields. Due to some extra cleverness, I have “unused methods” and “never assigned fields” all around the project. ![]() Eclipse feels smoother (I know that’s not a proper argument, but I can’t be more precise) I read somewhere that they were excessively repainting the screen elements, so that might be the explanation. There is some minor delay that I can’t define well, but “I feel it”. I don’t have representative benchmarks of that, and I know that my 8 GB RAM home machine is way to small for development nowadays, but still.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |