Post

Soon I start building the most ambitious thing I've attempted with Hologram (my full-stack Elixir framework): the Local-First data layer. Your app keeps its data locally, syncs in the background, and keeps working offline - all of it written in Elixir.

0 reposts10 likes

So I'm turning the research into a landscape analysis blog post. Before I write it - what would you want it to answer? How the engines compare? Where they fall short? What any of this means for Elixir?

I came out with a pile of notes and a few opinions I didn't expect to have. Some of it made it into my ElixirConf EU talk this year - I'll share the video here once it's out. (And the regular releases keep coming while I work on this - v0.10 went out this week, about a month after v0.9.)

Ambitious enough that before writing any code, I spent the past months studying every serious sync engine out there - Electric, Zero, Automerge, Jazz and friends.

Neither - Hologram's a full-stack framework, not just a runtime. It rebuilds the Elixir runtime in JS (not WASM), tuned for small bundles and lock-step with the event loop, with the local-first layer built on top.

I see, Impressive! I thought "full -stack" just meant the traditional web framework back-end layers, but you are being quite a bit more literal.