My language of choice is Rust, but I’d go with Gleam in a heartbeat if I:
- Were working on a team with junior engineers
- Building a web app
- On a passion project, or in a business context where the lack of ecosystem etc. wasn’t a concern
For my own projects or with other senior folks, Rust’s complexity is a price you pay once and you reap the rewards forever afterwards. But Gleam’s simplicity would really shine in an organization with a wider range of experience levels.
My biggest complaint besides the obvious ecosystem stuff is that the most popular frontend library leaves something to be desired. It’s SPA-first, which seems like a very strange decision to make in 2025.
This resonated with me. Will use it in the future when I explain why I use Rust for almost everything.
It won’t be as elegant as Lustre, but I figure it may be helpful for adoption if React/Vue/Svelte can be used on the front end.
With the server-side routing, Inertia doesn’t feel quite so SPA-first.
Then one could write performance critical sections in rust and interface with it more easily.
It’s not! Lustre is very flexible and can be used in many different ways, including LiveView style server components. It’s not limited to SPA.
One interesting aspect of this approach is that if you want Gleam’s type safety guarantees, it requires explicitly decoding dynamic terms into Gleam data structures.
The latest version of Glyn amortises the cost of the decoding by performing it once per cluster node, then using the local typed messaging system to deliver the message to local subscribers.
roxolotl•5mo ago
Tiny bit of self promotion since it’s easier to link out to my own words than type them again. Typed actors in Gleam are so damn powerful. https://www.tcrez.dev/2025-07-13-gleam-otp-101.html
mbuhot•5mo ago
okkdev•5mo ago