I don't have any idea at the moment - it's really not that high on my priority list I'm afraid, and it depends a lot on distributors and the volume of boards that I sell.
There's an optimisation that will make normal arrays of numbers twice as efficient, and there's another that will add another 20% more variables. They're all things that I think should take priority, as they benefit even existing users.
The existing parts will be future proof. The whole point of Espruino is to provide a JavaScript interpreter that runs on cheap microcontrollers - I don't intend to start requiring more complex parts any time soon.
I'm not really running into boundaries with the existing firmware either... I use some compile flags which means it only just fits, but that's intentional. I can get another 50kB if I need just by changing one character in the Makefile, and there's still plenty of room for optimisation in Espruino's innards too.
It's really surprising how few people are actually hitting memory issues right now. You can actually do a hell of a lot with what's available, and I wonder how many projects would fit in 96kB that wouldn't fit in 48.
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.
Hi Alex,
I don't have any idea at the moment - it's really not that high on my priority list I'm afraid, and it depends a lot on distributors and the volume of boards that I sell.
There's an optimisation that will make normal arrays of numbers twice as efficient, and there's another that will add another 20% more variables. They're all things that I think should take priority, as they benefit even existing users.
The existing parts will be future proof. The whole point of Espruino is to provide a JavaScript interpreter that runs on cheap microcontrollers - I don't intend to start requiring more complex parts any time soon.
I'm not really running into boundaries with the existing firmware either... I use some compile flags which means it only just fits, but that's intentional. I can get another 50kB if I need just by changing one character in the Makefile, and there's still plenty of room for optimisation in Espruino's innards too.
It's really surprising how few people are actually hitting memory issues right now. You can actually do a hell of a lot with what's available, and I wonder how many projects would fit in 96kB that wouldn't fit in 48.