submillisecond VS wasm-service

I believe that https://github.com/lunatic-solutions/submillisecond wants to be that.

Lunatic is exciting, I'm keeping an eye especially on the submillisecond web framework that targets wasm: https://github.com/lunatic-solutions/submillisecond

- https://github.com/lunatic-solutions/submillisecond/tree/mai...

Lunatic runtime for Rust to avoid the async parts might become quite nice in the future: https://github.com/lunatic-solutions/submillisecond

Not sure what it might take for someone to write database connectors for it but it does look promising.

What a coincidence, I was just discussing on discord a similar approach for our Rust web framework submillisecond[0].

Submillisecond uses lunatic to run Rust code compiled to WebAssembly on the backend. We are working on a LiveView-like library now. And one thing I would love to give developers for free is an offline-first experience. You write everything in Rust, compile it to WebAssembly, run it as a regular backend on lunatic, but also allow for moving the whole server into the browser for a offline experience. If SQLite is used for the DB, it could also potentially run in the browser.

This doesn't need to move the whole app into the browser, but could do so just for more latency sensitive workloads that don't fit LiveView well. Like form validation on every keypress, etc.

[0]: https://github.com/lunatic-solutions/submillisecond

Web socket support was added a few days ago[0], but it's still not part of a release. I will probably push out alpha1 tomorrow including it and a few other changes.

[0]: https://github.com/lunatic-solutions/submillisecond/pull/78

There is a rust one here: https://github.com/richardanaya/wasm-service

Check out the live demo! https://richardanaya.github.io/wasm-service/

Last month I contributed the todos functionality to this project.

I think this is a great idea and could eventually enable htmx projects to transition from server-side-only to being a PWA with very little code changes (given the right backend).

Unfortunately this particular implementation exhibits some blocking issues which I was not able to solve yet:

1. The Service Worker is eventually unloaded from memory, which means all data is lost because it currently stores everything in memory. This isn't a defect as much as it is lacking a persistence feature; this is a MVP (emphasis on minimal) after all. The most promising solution in my opinion would be to use the OPFS/File System Access API with SQLite, which is yet to be shipped in all browsers.

2. The bigger issue is that once the SW is unloaded it doesn't come back. The SW getting reaped after being idle is fine, that's part of the expected behavior. But there are no events or any other indication that it was disconnected, at some point it just stops intercepting requests. I don't know why. If anyone can chip in here to say why it does this and how I can detect or somehow restart SW fetch interception on demand I would be glad to hear it.

( For some more detail see the "# Remaining Issues" in my PR #5: https://github.com/richardanaya/wasm-service/pull/5 )

Once you have done that, run this: https://github.com/richardanaya/wasm-service, for better offline experience