Well, in my head, having the possibility to move help into the meta files is required. Otherwise, we *will* have file spewage in the future ("shit, we used ini and we can't move help into there? Um. So, let's make a .help file! whee!"). I'm against file spewage: I'd really only like to see .install, .inc, .module, and .meta (or some such).
Considering how the help hook currently works, can you think of a way not to have all help hooks loaded all the time to be able to run the help system.
Can I think of a way *right now*, on the spot? No. Do I know that there have been various desires to do so? Yes. Do I know that there is a belief that moving the help out of there will improve performance? Yes. Do I know that there's a desire to make handbook editing map sync more closely to module help editing? Yes. Do I want file spewage because we didn't make the "right" and "most flexible" decision? Absolutely not. Do I want the ability to move help into our meta info file? Yes. Am I thinking about that right now? Yes. Ignoring the technical limitations of moving help outside of .modules in general, do I believe that .ini files can satisfy the help desire? No. Do I see the move from .sql files to .install files being indicative of a future possibility with the non-logical .ini files? Yes. Do I want to make the same mistake? No. Help does not need to be there on node/13. No help has ever been displayed on that page. But, a lot of help text is actually loaded in memory on that page load. Should it? Not at all. -- Morbus Iff ( you are nothing without your robot car, NOTHING! ) Culture: http://www.disobey.com/ and http://www.gamegrene.com/ O'Reilly Author, Weblog, Cook: http://www.oreillynet.com/pub/au/779 icq: 2927491 / aim: akaMorbus / yahoo: morbus_iff / jabber.org: morbus