Ask HN: How to write OO JavaScript that is both readable and IDE-compatible?
The code now is more structured, clean, and obviously better.
My coworker is a super-great programmer, I personally respect him very much both humanly and professionaly, but this whole refactoring has made me thinking about one thing, and that is: IDE Compliance.
We are using an IDE (netbeans in this case) to develop our app, but I found that if we write JS this way the IDE won't give autocomplete suggestions decently. So, while we get all the beauty of OOP, we don't get to know what are the available methods of an object unless we "remember" them.
Personally I think this can and should be improved because if another person comes onto the team he/her wouldn't know how to interact with our "framework" unless he starts digging into the code.
What was your experience on this? Is there a way we can write clean OO JS code that is also indexable from an IDE?