submillisecond-live-vie VS submillisecond

I'm Bernard, the creator of lunatic. Great to see us back on HN and happy to answer any questions!

We have been busy pushing out a lot of new stuff. Recently we released a web framework [0] for Rust building on top of lunatic, and a live-view library [1] for crating full stack apps in Rust without JS. For now we are staying close to the Phoenix LiveView implementation, where everything is rendered on the backend and just a diff is sent over websockets to the frontend. But a big advantage of Wasm is that it runs in the browser too, so we hope to leverage this part to move some of the logic directly into the browser, like form checking, or offer a way to create offline-first experiences with the backend running as PWA in a service worker.

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

[1]: https://github.com/lunatic-solutions/submillisecond-live-vie...

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