2) We certainly don't want to bloat the system by including large widget libraries of which only a fraction will be used.
It all depends how things are built... Any system that does not implement a dependency driven loader, is not modularized along the dependencies, and has no builder, does certainly pull in more then what's needed.
Nobody goes to a (real) library and brings all titles home. A proper (AMD/dependency/loader/builder) setup pulls just the items of interrest at that particular scope of runtime.
Completely agree. However, many systems have some minimum overhead and the granularity of includes varies. We are actively working on trying to get sensible widget support, but I think you'll agree it's not a particularly easy decision.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
It all depends how things are built... Any system that does not implement a dependency driven loader, is not modularized along the dependencies, and has no builder, does certainly pull in more then what's needed.
Nobody goes to a (real) library and brings all titles home. A proper (AMD/dependency/loader/builder) setup pulls just the items of interrest at that particular scope of runtime.