This is really cool... since you know the guts, interfacing between compiled and interpreted can be very optimal (and programmer transparent). It is like REXX (on main frames and os/2) did as well as IBM's/OTI's Smalltalk... which compiled to the actual hardware and hid it within the actual file as property or loaded only the JIT stuff. Since JIT on espruino is not an option, why not doing it by the IDE on upload onto the board... I hope that referencing still goes through the JS-specific 'very late' binding... than there is no reason why js and compile js can not work in coexistence...
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.
This is really cool... since you know the guts, interfacing between compiled and interpreted can be very optimal (and programmer transparent). It is like REXX (on main frames and os/2) did as well as IBM's/OTI's Smalltalk... which compiled to the actual hardware and hid it within the actual file as property or loaded only the JIT stuff. Since JIT on espruino is not an option, why not doing it by the IDE on upload onto the board... I hope that referencing still goes through the JS-specific 'very late' binding... than there is no reason why js and compile js can not work in coexistence...