Congrats on the release @bartblast! 
thiagomajesk
bartblast
Creator of Hologram
At the low level the realtime layer sits on Phoenix.PubSub, the same primitive Phoenix.Channels builds on, so the ordering guarantee is identical. Hologram broadcasts go through Phoenix.PubSub.broadcast, and each instance’s downstream stream is a single process writing to a single connection, just like a channel pushing through one socket. So per instance you get FIFO in mailbox order, and cluster-wide neither one gives you a total order: two concurrent broadcasts from different processes or nodes can land in different orders on different subscribers in either system. Channels doesn’t buy you a stronger ordering guarantee here, it’s the same pub/sub primitive underneath.
And the server-vs-client framing is really about where state lives by default, not the transport. Hologram puts UI state on the client, so naive reconciliation lands there, but it’s the same Elixir server underneath, so you can keep authoritative state server-side and order or version it there just as you would with Channels.
0
bartblast
Creator of Hologram
f0rest8
bartblast
Creator of Hologram
billylanchantin
bartblast
Creator of Hologram
Quick update for anyone who’s already grabbed it: v0.9.1 is out 
It fixes a compile-time slowdown that can show up in projects with deeply nested templates - thanks @absowoot who flagged it. If you’re on v0.9, a quick bump keeps your builds fast.
Release notes: Release v0.9.1 · bartblast/hologram · GitHub
0
bartblast
Creator of Hologram
Good catch - thanks! with was indeed stale: it’s fully supported, so it’s now marked done. Your comment also prompted a wider pass, and the Features and Roadmap pages are both up to date now.
These had already shipped but were still mislabeled, and are now marked done:
withExpression- JS Interop
- Essential Stdlib Functions
- Bitwise Module Operators
- Exponentiation (
**) - VS Code Extension
- Server-Triggered Actions → Pub/Sub
One note on that last one: Server-Triggered Actions was originally scoped as a much simpler feature - just firing actions from server-side code. As I built it out, though, it grew into a full realtime layer, so it ended up shipping as Pub/Sub, which supersedes that narrower idea. More roadmap items coming soon - appreciate the nudge!
6