beam_languages VS submillisecond

Languages, and about languages, on the BEAM: https://github.com/llaisdy/beam_languages

PS: You might also find this interesting : https://www.grisp.org/

I thought this was a call for Standard ML or something a rather on the Erlang VM.

(I really enjoyed this article though!)

As far as I know theres a few implementations of ML like languages on the Erlang VM

https://github.com/llaisdy/beam_languages

caramel and alpaca are worth checking out.

Gleam doesn't look like a ML lang but has a lot of the same semantics of a ML lang

Have I got a link for you!

https://github.com/llaisdy/beam_languages

See you down the rabbit hole!

Elixir, LFE, etc. seem to work fine for the people who enjoy them.

https://github.com/llaisdy/beam_languages

LFE is Virding's himself, and has been around for longer than Erlang has been popular: Robert Virding - LFE - a lisp flavour on the Erlang VM (Lambda Days 2016) https://www.youtube.com/watch?v=Br2KY12LB2w

The Beam Languages repo is filled with projects to build on top of Erlang and the BEAM to take inspiration from.

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