...And the entire Windows API? Quite simply, you've shown why some of us prefer to work with compact frameworks in the online space. The normal web stack, as

...And the entire Windows API? Quite simply, you've shown why some of us prefer to work with compact frameworks in the online space. The normal web stack, as a vocabulary, is really only a few thousand "words" in size: HTTP verbs, HTML tags, CSS selectors, JavaScript/jQuery/etc. API, and your choice of agile web framework interfaces (perhaps with a little SQL mixed in for good measure). Once you're relatively literate in the weird pidgin that is the modern web stack, it's pretty easy to rely on the auto-complete engine already wired into your head. If your class member names are too long, or your method defs are buried inside some 10Kloc monster source file, perhaps you should consider some light refactoring to clean things up. Similarly, if you find yourself heavily relying on search-and-replace outside of single files, you may may have a bit of a coupling problem in your system.