PicoPico VS pyroscope-rs

You can download the cart here (the 3dsx file). If you have homebrew launcher, give it a try! As I said before, consider this broken/alpha. Bunny, Valdi and Celeste are mostly playable

Continue implementing PICO-8 on an ESP32 platform, trying to make it into a PCB with a friend's help

https://github.com/DavidVentura/PicoPico

This is a work in progress build of Pico-8, running on an ESP-32 (with 4MB PSRAM) The code is on github. There's no music support, audio kinda works. There's an SDL backend to test the implementation on PC

A handheld, esp32-based implementation of the pico-8[0] console. Basics work already, sidetracked into writing a terrible Lua to C++ compiler to squeeze some extra performance out of some pathological-case games.

Lives at https://github.com/davidventura/picopico

This looks excellent! I'll definitely try to learn a bit of what you've done

I'm making a similar project; a handheld Pico-8 console: https://github.com/DavidVentura/PicoPico/ although currently I'm stuck in the process of writing a half-working Lua-to-C++ compiler

I saw Pico8 a while ago and really liked it! Now I'm trying to make it "real", by creating a physical console that implements the API: https://github.com/DavidVentura/PicoPico

It's heavily incomplete, but it runs "Celeste" on an ESP32. Some small games also run in the Raspberry Pico (RP2040), but it does not have enough RAM for medium-large games.

A general purpose profiler: https://github.com/pyroscope-io/pyroscope-rs

If someone is interested in this space, feel free to reach me!

I feel some of the OP points. I was working on a profiling agent lately, and one of the issues was running it on multiple platforms (just the four big ones linux/mac-x86/arm) on FFI (because it'll be run directly from python/ruby/etc...) and preferably having the thing just work without having to install or configure any dependencies.

Like OP I hit two walls: libunwind, and linking. For libunwind, I ended up downloading/compiling manually; and for linking there is auditwheel[1]. Although it is a Python tool, I did actually end up using for Ruby (by creating a "fake python package", and then copying the linked dependencies).

It was at that time that I learned about linking for dynamic libraries, patchelf and there is really no single/established tool to do this. I thought there should be something but most people seem to install the dependencies with any certain software. I also found, the hard way, that you still have to deal with gcc/c when working with Rust. It does isolate you from many stuff, but for many things there is no work around.

There is a performance hit to this strategy, however, since shared dynamic libraries will be used by all the running programs that need them; whereas my solution will run its own instance. It made me wonder if wasm will come up with something similar without affecting portability.

Finally, the project is open source and you can browse the code here: https://github.com/pyroscope-io/pyroscope-rs

[1]: https://github.com/pypa/auditwheel

Version 0.5 is now live!: https://github.com/pyroscope-io/pyroscope-rs

Working on https://github.com/pyroscope-io/pyroscope-rs A profiling solution for Rust and other languages.

Thanks to the maintainers at pprof-rs for helping us figure out how we can modify their profiler to create our rust agent (https://github.com/pyroscope-io/pyroscope-rs).