4 ms·
Personal anecdote: LiveView is absurd. It's the biggest change I've experienced in web development since Rails v1. I've been able to build rich, interactive, g
by heeton 5y ago
Personal anecdote: LiveView is absurd. It's the biggest change I've experienced in web development since Rails v1.
I've been able to build rich, interactive, games without a single line of Javascript. It takes complicated server / api / front-end build projects and results in literally 1/10th the amount of code for the same result.
It's one of the few times in our world that the technology isn't just "new and cool" but "fundamentally better".
- rvense 5y agoI really wanted to use it at my last job, where we had a Go backend and a React SPA and a sprawling, ad hoc RESTish API in between that was only used by the SPA. We were mostly split between Reactors and Gophers, and the amount of time we spent arguing about the API and implementing it... I'd say was easily one third of the word, if not more, that would have just gone away if we didn't have to worry about the details of the data we were moving back and forth. My current job is a bit too front-end heavy for LiveView to make sense. But I still keep an eye on Phoenix. It really feels like it could be a secret weapon, at least until every one else adopts a similar pattern.
- redbar0n 5y agoThe time spent on discussing data exchange details (protocol) between teams is regained in their ability to work largely independently of one another (without constant sync).