267 karma · joined December 17, 2008
- https://donnie.com - https://www.linkedin.com/in/donnieflood - https://github.com/floodfx
donnie at floodx dot com
Currently CEO at ContextBridge (https://contextbridge.ai)
There isn't an official "protocol" so I had to figure it out by watching the WS traffic and determining how it worked which was fun if not tedious. That said, the more I learned, the more I was impressed by the efficiency and the programming model which felt simpler yet more powerful than SPAs.
I did get to a point where I just got too busy to keep up and over the last couple of years things have changed a bit on the "protocol" side.
But recently (a week ago-ish), I started poking at the old LiveViewJS repo with the help of coding agents. Now that Phoenix is past 1.0 and the JS runtimes (Node, Deno, Bun) have more overlap in terms of APIs and library support, I think it will be more straight forward and frankly easier to get and stay at parity.
Getting a plan isn't a panacea but is a better way to limit downstream slop than just vibing without one.
This looks interesting nonetheless.
These are uber-personalized feeds optimized to keep you scrolling to the next item (story / video / post) so companies can show more ads.
"Social media" is a textbook example of a euphemism. We should be calling this what it is: "addiction feeds".
Great application of spaced repetition beyond cards.
Makes me think a bit about how negative content engages more people. Is this the same with people who don't like change? Not liking change activates people more than people who do like change?
Great idea on the collectible stickers!
This is meant to be used while sitting with the kid as opposed to handing them my phone right?
- Bullet-proof N+1 prevention,
- Tracking loaded relation/subgraph state in the type system, and
- Backend reactivity, for declarative cross-entity validation rules and reactive fields.
Wow!
Disclaimer: I wrote or helped write the first three.
I used it to support a LiveView implementation for Java: https://github.com/floodfx/undead
Sure the syntax isn't "pretty" but understandable and you get used to it like anything else.
You can think about it as a server-rendered HTML page that gets updated via Websocket updates.
That doesn't really do it justice either. I think writing a little bit of code and running a LiveView server is probably the best way to truly grok it.
Like any new paradigm, it takes a bit of a mind shift to see the value.
If you can, try running the Undead example server by downloading the repo and running:
`mvn package exec:exec`