PicoPico VS upspin

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.

Super intriguing. Thanks for sharing!

It reminds me a bit of an early Go project called Upspin [1]. And also a bit of Solid [2]. Did you get any inspiration from them?

What excites me about your project is that you're addressing the elephant in the room when it comes to data sovereignty (~nobody wants to self-host a personal database but their personal devices aren't publicly accessible) in an elegant way.

By storing the data on my personal device and (presumably?) paying for a managed relay (and maybe an encrypted backup), I can keep my data in my physical possession, but I won't have to host anything on my own. Is that the idea?

https://upspin.io/

There are a few Go projects meant to be learned from:

- https://github.com/pion/opus for to learn audio

- https://github.com/benbjohnson/wtf for overall production quality

- https://github.com/upspin/upspin difficult to explain, personally I'm not a fan of the errors

You could also take a look at some real-world open-source projects. I like upspin for its idiomatic approach.

For example, Rob Pike's upspin places all its validations in the separate package. Do you agree with that approach? Which yet proven options there are?

Just a few projects that could perhaps interest you in terms of design of your own solution :

Upspin: https://upspin.io/

The early error wrapping work which emerged out of the Upspin project, that eventually made its way into the errors package, included stack traces in the wrap error. This would provide exactly what it appears you seek.