I'm sure this topics have been discussed at some time but recently I read opposite opinions about them.
Is splitting addons in modules really useful at all? I mean it probably makes sense with big addons like cartographer putting for example the gatherer part in a module. But does a small AddOn like AuldLangSyne really benefit from several small modules?
Isn't the overhead caused by that much bigger than the memory/cpu-usage saved? Especially if the modules get load anyway by the user?
I read also that disembedding shortens the initial loading time, but uses much more memory/cpu because a lot of libraries get load loaded regardless if they are used. Is that true? Should disembedding used only for debugging?
As I understand it, modules leverage the load on demand system to reduce resources used by unused portions of an addon. I'm not aware of any / much overhead. It is a pain in the butt though when you manually manage your addons and you have pages and pages of crap in the addon directory. I prefer to leave them packed up and delete the modules I don't use.
Keep in mind memory is cheap. WoW on my system uses about 800 megs of 1.5 gigs free. The worst addon load I've ever seen is shy of a 100 megs. IMO people worry too much about memory used.
Disembedding should only be done by users who know what they are doing. It's not how the libraries were designed to be used. Too many people complain an addon isn't working because they disembedded, then forgot a library and don't understand the error that causes. Personally I haven't found it to affect load times significantly enough for me to be bothered with the hassle.
Yes. Each Addon folder creats incurs a small overhead. When deciding on how I was going to support not-loading modules. I concluded that the cost of using separate addons outwighed the benefit of using them.
As an alternative to separate addons. Take a look at how Prat3 does it.