▲ | lawn 4 days ago | |||||||
I haven't seen Hologram before. What an ambitious and exciting project! I see that you've been focusing on the performance aspect but I see a big benefit with the offline first use-case. It would be nice to have built-in support for syncing any changes when the client comes back online as it would remove the biggest issue with LiveView based websites (that they stop functioning if you lose connection). For example, a simple todo list where you can check off items offline and when you go online they're sent to the server? | ||||||||
▲ | bartblast 2 days ago | parent [-] | |||||||
Thanks for the kind words! You're right about the offline-first benefits - that's definitely part of what will eventually be Hologram's local-first philosophy and it's on the roadmap (https://hologram.page/docs/roadmap). I needed to get the performance to a usable level in v0.5.0 because the previous iteration was quite slow, and I was concerned about getting bad press early on (there was actually a previous HN discussion about Hologram's performance issues). The slowness also prevented implementing latency-sensitive features like the real-time pointer/mouse events you see in the SVG drawing demo - which are really Hologram's main use case. It's already blazing fast now, though I haven't squeezed max performance yet - there's still room for improvement. There are still some high-priority features that need to be implemented first before tackling the local-first capabilities. The CRDT implementation in this release is part of the foundation for those distributed/sync features, but there's more foundational work needed. | ||||||||
|