Can you please share the reasons for moving from RP2040 Chip to ESP32 about picopico HOT 4 CLOSED

Hi

I had the exact same idea initially; there's indeed 64KB of "machine memory" (with 32KB of scratch and 32KB affecting console state).. but there's also this -- you can allocate up to 2MB of Lua objects; ie: create a table with 20000 entries

Everything else can fit in memory, if barely, but the game-object memory won't.

The "abandoning" is a bit strong -- if you look at the pico_backend.c -- it is very small, at the moment the only thing missing from it is a way to play SFX, the rest works, so you can give it a shot

from picopico.

I am thinking of a precompiled Lua code instead of real time interpreting. This should allow us to store the Lua memory 2mb in flash storage. Does it make sense?

from picopico.

Pre-compiling would help a bit; it is in fact something I'm thinking about -- however you can always do this

function f()
        t = {}
        for var=1,100000 do
                t[var] = 5
        end     
end                    

f()

and it won't execute to completion on the Pico, there's no RAM to keep the table t

from picopico.

Hey!
This does not currently work well, partly because it is incomplete and partly because I don't know enough about C++ to generate code properly, but I've started a Lua to C++ compiler here: https://github.com/DavidVentura/lua-but-worse

from picopico.