4 ms·
I don’t know if the author intended to be “local first- adjacent” with this project, but I am seeing a lot of wasm-target projects lately, including replicated
by threecheese 2y ago
I don’t know if the author intended to be “local first- adjacent” with this project, but I am seeing a lot of wasm-target projects lately, including replicated databases, and I wonder if this project isn’t a peek at what a truly distributed (browser-to-browser) workload might look like. This project persists the system config in GitHub, but if the components are wasm then there’s at a chance that they can use that provision themselves in every browser.
Imagine a workload where a client does their own compute, by provisioning worker components locally and retrieving only shared data from your systems - how much cheaper would your hosting costs be?!
- hosh 2y agoThanks for articulating that. I was groping around for something along those lines — going beyond easy self-hosted to local-first deployment. Considering the web3 origins, I wonder if the project founders had that in mind as well. There was a different, recent HN post about scoped propogators, which I find to have a lot of good potential for people to write and apply local customizations for their own apps. I don’t know if those are the killer use case for this, but I think ideas along these lines takes it further out of alignment with incentives for business models.