Otherwise we'll initialize with dumb values and refresh it when shown, which
isn't all that effective.
that depends how heavy the load() implementation is...
both ways are not optimal..
this behavior comes from KCModule, where the module nevel loads itself and a load() must be called from outside.
here may be worth doing that even if it's two loads as would avoid a binding reevaluation. othe the other hand.. a config read more, hmmm