> To avoid dropping user events on the client side a small, inline library listens for user events at the root and replays them.
Im curious about this sentence.
Does that mean they deliver the replay system to the client first, and replay early events back to the server before full interactivity is set up client side?
I tried Angular after many years and it feels very difficult to adapt even though it is not where you can make mistakes easily when compared to other frameworks and when I saw this title, I thought they are trying to address the problem.
Yak Yak Yak, another framework which solves nothing in this world of despair. When has a framework ever solved a war?
"Use us, because we are google"; I'm tired of this walled garden sheep and pony show. It's a loop on repeat.
Show me something. Show me something of worth that's come from these frameworks. Something that cures my cynicism, because all I see from the internet and the future being more restricted with entry points and exile because your not following suit.
Next week: some other framework we should all use. Maybe I should equip Cloudflare to save me from the downvoting....
Yak Yak Yak, another framework which solves nothing in this world of despair. When has a framework ever solved a war?
"Use us, because we are google"; I'm tired of this walled garden sheep and pony show. It's a loop on repeat.
Show me something. Show me something of worth that's come from these frameworks. Something that cures my cynicism, because all I see from the internet and the future being more restricted with entry points and exile because your not following suit.
Next week: some other framework we should all use.
Maybe I should equip Cloudflare to save me from the downvoting.
https://news.ycombinator.com/item?id=39777267