Integration boils down to 'who owns the pins and the other resources (timers, interrupts)...'. Espruino is usually standalone and owns it all in a very integrated way between hardware side and application / programming side... Similar is RTOS: it provides interfaces to the resources and the application has to use them... Mapping/connecting this underlaying resources into Espruino becomes an issue for time sensitive tasks, and both environments do not always share the same solution approach.
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.
Integration boils down to 'who owns the pins and the other resources (timers, interrupts)...'. Espruino is usually standalone and owns it all in a very integrated way between hardware side and application / programming side... Similar is RTOS: it provides interfaces to the resources and the application has to use them... Mapping/connecting this underlaying resources into Espruino becomes an issue for time sensitive tasks, and both environments do not always share the same solution approach.