I’ve recently started using Netbeans for its profiler (I have some code that won’t run in 1.5G and I need to work out why) and while the profiler is vastly better than what Eclipse’s TPTP project provides and Netbeans is vastly better than it was when I first tried it 5+ years ago, there are some constant annoyances; little things that Eclipse does that I rely on all the time (non-exhaustive and in no particular order):
- highlighting all occurrences of the current element (if the cursor is on a var, method or field, then all occurrences in the file are highlighted, including markers to the right of the scrollbar so I can see where it’s used elsewhere in the file)
- toggle of comment/uncomment; netbeans has these has two separate commands (why would I ever want to comment an already commented line?)
- support for generics in completion (and smart filtering wrt completion in general) is woeful; if I have a variable s declared to be of type java.util.Set<Foo> and I type s = new then I expect completion to a) offer only (non-abstract) classes that implement the Set inteface, and b) throw in the appropriate generics stuff as well, e.g., HashSet<Foo> rather than just HashSet.
- multiple launch profiles
- junit integration
Trackbacks & Pingbacks 1
[...] Netbeans gripes [...]
Post a Comment
You must be logged in to post a comment.