RE: https://floofy.tech/@jump_spider/117398705006373620
So hooking a React front end with a Goblins wasm module doesn't seem to be an established practice. I tried to reassess my goals with the tech choices, noting that React is good at presentation and client state management and Goblins is essentially a transport layer with security capabilities on the data it transports. So the idea is to encapsulate state inside React and propagate that state to other peers via Goblins.
There are a few problems with this though.
- The boundary between wasm and js isn't insurmountable but it makes things trickier.
- I think I lose the benefits of capabilities once the state passes to another React peer. I'm still musing on this point, maybe it's possible with sturdyrefs and/or the sealer tool in Goblins?
- Like I hinted at, all the prior art I've found is a different pattern entirely, where dom manipulation is handed to the Scheme wasm. Blazing your own trail is obviously more difficult.
OK, I've picked up enough essential Guile Scheme to feel comfortable trying to hack with Spritely Goblins now.
Aiming towards a web app that allows tracking shared expenses. Starting with the Guile part, wrapping it all in an event loop, and compiling it to wasm with Hoot. Then write up the UI shell...haven't decided with what yet, but leaning towards either React with Typescript or Gleam? Should probably keep it simple.
Then...then I see if I can extend it to be a p2p application.
