I think , from my personal point of view , this is one of the few things missing Espruino . The speed , compilation and/or pseudocode/asembler generation that are key to success of Espruino .
Most functions that are programmed in a microcontroller pro/hobby, like a leds, some analog readings on these calculations, etc ... every 100ms or a reasonable time, do not penalize the overall implementation of these "events" , but if we add too many other low priority process, over a others CPU-time with the run-time-compilation, and if the project is complicated , it can penalize both implementation and memory usage. The compilation before flash, and the generation of ByteCode (outher o inside microcotroller), is great!
I encourage you dig splendid views to ELUA project (http://www.eluaproject.net/overview/status). A "languaje script " based on Lua, very mature, and where use of compiling and generating ByteCode done, even when the "source code" ( script ) is stored in Flash memory or a SDCard, less flash memory usage, better speed and low RAM. Lua like a language, I do not like too much. I prefer Javascript. See Cross-compiling at http://www.eluaproject.net/doc/v0.8/en_using.html
Thank you for this fantastic tool. You encouragement to proceed further in this line ( ByteCode / compilation ) because I believe that is the only (or can be a) problem for Freduino.
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.
I think , from my personal point of view , this is one of the few things missing Espruino . The speed , compilation and/or pseudocode/asembler generation that are key to success of Espruino .
Most functions that are programmed in a microcontroller pro/hobby, like a leds, some analog readings on these calculations, etc ... every 100ms or a reasonable time, do not penalize the overall implementation of these "events" , but if we add too many other low priority process, over a others CPU-time with the run-time-compilation, and if the project is complicated , it can penalize both implementation and memory usage. The compilation before flash, and the generation of ByteCode (outher o inside microcotroller), is great!
I encourage you dig splendid views to ELUA project (http://www.eluaproject.net/overview/status). A "languaje script " based on Lua, very mature, and where use of compiling and generating ByteCode done, even when the "source code" ( script ) is stored in Flash memory or a SDCard, less flash memory usage, better speed and low RAM. Lua like a language, I do not like too much. I prefer Javascript. See Cross-compiling at http://www.eluaproject.net/doc/v0.8/en_using.html
Thank you for this fantastic tool. You encouragement to proceed further in this line ( ByteCode / compilation ) because I believe that is the only (or can be a) problem for Freduino.