[jamesgeck0]

IIRC, the browser builds of Pyxel games end up pulling down 30mb+ of Python libraries, which seems a bit overkill for little pixel games.

TIC-80 is probably the closest open source thing to PICO-8. The browser builds ran 10% slower than the desktop app last I tried. It doesn't have a "CPU budget," so it's possible to write inefficient code that works fine on powerful machines but not slower ones.

[vunderba]

So I just ran a test deploy of a Pyxel little animated star field:

https://gondolaprime.pw/games/starfield/index.html

Developer console shows approx ~7MB transferred. Still more than I would have expected for literally just a small looping animation but a bit better than 30MB at least.

Maybe there's been some progress on this front.

Thanks for the TIC-80 recommendation - I really like that it supports multiple langs (Lua, JS, Python, etc) - that's some great flexibility.

EDIT: It looks like TIC-80 games pull a tic80.wasm file which is approximately ~6MB in size. I'd say Pyxel and TIC-80 are roughly comparable at least with respect to bundle size.

https://tic80.com/js/1.1.2837/tic80.wasm

[filleduchaos]

> Developer console shows approx ~7MB transferred

Bytes transferred over the wire don't equal actual file size (due to gzipping, etc). Your page actually weighs 21MB.

[vunderba]

Yes, I'm well aware of that - but your average viewer isn't going to notice expanded resources, however they ARE going to notice things like time-to-first-byte and network transfer.

EDIT: Just to be clear since I can't edit the older comment - instead of bundle size it would have been better to say that the "network transfer size" is roughly comparable.