if a js codebase is structured appropriately, webstorm does an excellent job of intellisense and refactoring. netbeans 7.2 does an adequate job, but oracle ruin

if a js codebase is structured appropriately, webstorm does an excellent job of intellisense and refactoring. netbeans 7.2 does an adequate job, but oracle ruined the js support when they bought sun (didn't like the rhino license - they've been pedaling backwards ever since) the biggest issue i see, is that the "dialect" that you need to follow to enable the intellisense isn't well-defined. what seems to work for me: 1. explicitly define constructors 2. explicitly define the prototype 3. use jsdocs if you're using inheritance 4. initialize object literals (even if they get overwritten immediately)