Let the Lua bashing begin!

Paul Sokolovsky 2014-06-26 21:58:45 -07:00
parent b56d659b7d
commit cc8a2c21d1
1 changed files with 8 additions and 0 deletions

8
MicroPythonVsELua.md Normal file

@ -0,0 +1,8 @@
1. Latest release of Lua is 5.2. eLua is based on Lua 5.1.4, and this fact is not widely publicized. (ref: https://github.com/elua/elua/blob/master/src/lua/lua.h) uPy is based on the latest Python release, 3.4 (Note: over time, uPy will certainly linger with updates, too).
2. eLua, with LTR patch, boasts only 5.42K RAM usage after book, down from ~25K with unpatched Lua. (ref: http://www.eluaproject.net/doc/v0.9/en_arch_ltr.html). uPy offers ~540 *bytes* usage after boot (10 times less than patched eLua), and truly can boot and accept commands with 2K heap.
3. Just a quote (http://www.eluaproject.net/doc/v0.9/en_elua_egc.html):
> The EGC (Emergency Garbage Collector) patch [...], what it does is that it lets you run a garbage collection cycle in Lua in a low memory situation, from inside Lua's memory allocation function (something that the current version of Lua can't do out of the box).
That's unheard of. In uPy, garbage collection exactly runs when memory allocator can't find enough memory, as a native feature. Note that by "current version of Lua" the previous version of Lua is meant (see above). 5.2 appear to have native support for what most people do consider garbage collection in the first place.