4 ms·

I have been meaning to play around with Elixir, Phoenix and LiveView for a while, it seems like it could replace client-side JS frameworks (e.g. React) for many

by mxstbr 7y ago

I have been meaning to play around with Elixir, Phoenix and LiveView for a while, it seems like it could replace client-side JS frameworks (e.g. React) for many use cases, especially the ones that already fully use server-side rendering. Has anybody with lots of React experience made that switch? How is it going?

elcritch 7y ago
I switched my work project from Vue (which worked pretty well) to LiveView, and I’m not looking back. As the article mentions, not having to run a javascript build chain is fantastic. Writing modern JS isn’t too bad, but the complexity of writing a data api (whether JSON/rest, websockets, etc) on both the server and then client, and handling JS async data retrieval methods, is a huge turn off to me for writing new features. At least for me, being the solo developer. Big teams might find the data/UI split convenient for other reasons. Plus, it’s fast. Rather it feels faster than it should be. Perhaps since instead of waiting for JS to retrieve data, parse it, and render, and then update, you just need the JS to update the DOM once the data arrives. Of course my vue pages were using REST endpoints for data so perhaps a websocketed vue page would feel more responsive. LiveView still has a bit of maturing to do, but I’m really enjoying it. I’m really bullish that writing dashboards, admin pages, internal corporate tools can all be done an order of magnitude easier with LiveView or similar while still scaling decently.
- 1_player 7y ago
  Same here, we just deployed a React/Next.js app and it's been a veritable nightmare. Productivity was much worse than a normal server-side framework with a JS layer on top, especially since we've got experience with Elixir which has worked great for us. Soon we're starting another project, and we'll go with Phoenix (which we're already using as a backend and GraphQL server) with LiveView sprinkled here and there where we need better interactivity.
deleted 7y ago
[deleted]

by mxstbr 7y ago

elcritch 7y ago

I switched my work project from Vue (which worked pretty well) to LiveView, and I’m not looking back. As the article mentions, not having to run a javascript build chain is fantastic. Writing modern JS isn’t too bad, but the complexity of writing a data api (whether JSON/rest, websockets, etc) on both the server and then client, and handling JS async data retrieval methods, is a huge turn off to me for writing new features. At least for me, being the solo developer. Big teams might find the data/UI split convenient for other reasons. Plus, it’s fast. Rather it feels faster than it should be. Perhaps since instead of waiting for JS to retrieve data, parse it, and render, and then update, you just need the JS to update the DOM once the data arrives. Of course my vue pages were using REST endpoints for data so perhaps a websocketed vue page would feel more responsive. LiveView still has a bit of maturing to do, but I’m really enjoying it. I’m really bullish that writing dashboards, admin pages, internal corporate tools can all be done an order of magnitude easier with LiveView or similar while still scaling decently.

1_player 7y ago
Same here, we just deployed a React/Next.js app and it's been a veritable nightmare. Productivity was much worse than a normal server-side framework with a JS layer on top, especially since we've got experience with Elixir which has worked great for us. Soon we're starting another project, and we'll go with Phoenix (which we're already using as a backend and GraphQL server) with LiveView sprinkled here and there where we need better interactivity.

deleted 7y ago

[deleted]