Is there maybe a middle ground?
You could use conditional loading. This will benefit your runtimes in cases where the code to be executed only requires a small number out of the 85 packages which you have, ie. it saves time by not loading maybe 80 files that it won't ever use. There are a number of ways to achieve this and the one which will be most effective for you depends on what your entire codebase does, how scripts will use the modules and how modules will use each other. What you've shown in your stylised example is a 2-tier hierarchy. Is it the same the whole way through?
In reply to Re: Splitting large module
by hippo
in thread Splitting large module
by jimmygoogle
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |