It could be a good idea, yes. Something in the modules folder will get packaged in with each app and shouldn't take a bunch of extra memory. I think the issue with a 'core' library is stuff always gets added to it, and then to use two functions you end up having to pull in something with another 20 you don't care about :)
I'd argue that maybe we should enforce settings.json' so just require('Settings').get('app', 'option.to.get', 'default') might be better, and it'd mean less chance of bugs?
If we find it's something that every device is using, it could always be built into Bangle.js at a later date I guess?
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 could be a good idea, yes. Something in the
modules
folder will get packaged in with each app and shouldn't take a bunch of extra memory. I think the issue with a 'core' library is stuff always gets added to it, and then to use two functions you end up having to pull in something with another 20 you don't care about :)I'd argue that maybe we should enforce
settings.json'
so justrequire('Settings').get('app', 'option.to.get', 'default')
might be better, and it'd mean less chance of bugs?If we find it's something that every device is using, it could always be built into Bangle.js at a later date I guess?