> I believe a chip with 512k of RAM is good for a lot of real world eLua
applications. <Bogdan Marinescu>
examples I referenced?
> I don't think Lua is taking lot of RAM, all dynamic languages that I know
of need a lot of RAM (for good reasons) . <Bogdan Marinescu>
There is an idea that has been rattling about in my mind for a few years
now, but it may still be a little half-baked. This is that it should be
possible to allocate the bytecodes of functions/closures separately from any
required volatile storage (for example upvalues). The latter would be stored
in RAM, while the bytecodes would be stored as immutable strings (strings in
Lua already being byte-safe and immutable).
intrinsically event-driven it fits well with interrupt-driven
microcontroller applications, but compared to Lua it is an ugly, bloated
language, and Python is barely better without even the advantage of being
But I think it would be relatively easy to write an
event/interrupt driven scheduler for Lua coroutines.