pohmelie wrote:
I got your message.
I hope you did, and it's not "you better not use uPy on anything but microcontroller", but: "we're well aware that uPy isn't the only small language, and there's a competition. But then we exactly try to differentiate not just in language syntax, but also in other things, like going (or being able to go) where they couldn't reach."
that's why I came back to Lua and later to micropython, since python syntax is much better than Lua for me
So, if you want to hear more of that rant, that's exactly the problem. It's not Lua's fault that LuCI is works so slow. It's just written that way. But the fact that LuCI is written that way *is* Lua's fault. Because per my theory, many people choose Lua due to lack of alternative, and then when did what they had to do with it, they aren't interested to look back how well it works and optimize it. Because well, working with Lua isn't much fun. Python is a pleasure to work with, and we'd like it to be viable alternative even for the most embedded and resource-constrained usages. (Well, that's my agenda for sure).
but Lua coroutines is better, than python though
Lua coroutines are Stackless Python tasklets. And Stackless Python is around for many-many years. You should mind though why Stackless wasn't merged into mainline - because such non-lexical coroutines were deemed too confusing/dangerous. MicroPython supports stackless mode, the reason I didn't implement Lua-style coroutines is because I can't do it all myself. Interested parties are welcome to look into it.