You are reading a single comment by @allObjects and its replies.
Click here to read the full conversation.
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.
@allObjects
Going for two Espruino execution threads - one on each core - is for sure a good idea... but there is caution to be applied: JavaScript is by definition a single threaded execution. This makes it so easy to use... This fact is already compromised in some browsers that have a separate system io thread that is for entry fields not (anymore) synchronized with the events handling of attached JavaScript handling and causes quite nice challenges for implementing a solid working type ahead... To use one core for all (most) of the hardware event handling and native implemented code and leave the other core (as much as possible) 'free' for or busy with JavaScript execution is already a great progress and does not create challenges - last but not least in memory handling etc... otherwise we can then go right away to a Java VM like implementation... for which we for sure do not have the memory resources...