The improvements are pretty much the same as between clock and launcher minus the CRC32 check for changes.
Checking for loadWidgets everytime would take between around 200ms and 1000ms, so essentially eating all improvements. Caching the results and just checking the CRC takes 30ms-150ms.
Assuming a 300ms boot there is a 2x to 5x decrease in loading time from launcher. My bloated bangle install takes a lot longer than 300ms to boot ;)
I would not install this by default or integrate in firmware at this point in time either. Since it has no dependencies and "only" applies what is already done in .bootcde to other loads it should not have that many side effects (there are probably some with other apps redefining load). After leaving an app there is still a full reload every time as long as apps do not widely implement remove.
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.
The improvements are pretty much the same as between clock and launcher minus the CRC32 check for changes.
Checking for
loadWidgets
everytime would take between around 200ms and 1000ms, so essentially eating all improvements. Caching the results and just checking the CRC takes 30ms-150ms.Assuming a 300ms boot there is a 2x to 5x decrease in loading time from launcher. My bloated bangle install takes a lot longer than 300ms to boot ;)
I would not install this by default or integrate in firmware at this point in time either. Since it has no dependencies and "only" applies what is already done in
.bootcde
to other loads it should not have that many side effects (there are probably some with other apps redefiningload
). After leaving an app there is still a full reload every time as long as apps do not widely implementremove
.