3 ms·
I’ve invested a lot of time into both Go and Elixir. I like both languages a lot. My anecdotal view of the marketplace is that Elixir recruitment emails tend t
by aczerepinski 7y ago
I’ve invested a lot of time into both Go and Elixir. I like both languages a lot.
My anecdotal view of the marketplace is that Elixir recruitment emails tend to come from startups looking for their 2nd or 3rd dev, usually full stack, and the salaries are nothing special. Go recruitment emails tend to come from bigger companies looking for backend devs, often hoping for kubernetes experience too, and the pay is higher.
I built an internal service with LiveView at work and I loved it. I gave a presentation about how it all works and was hoping it would catch on. It didn’t. The front end team would probably mutiny if we told them to give up React and level up their LiveView skills.
If I were running a web business as a solo founder I would 100% want to use LiveView. As a dev on a larger team that already has specialization it’s a tougher sell.
- leorio 7y agowhat would you say are the benefits of using LiveView over react?
- rvense 7y agoWith LiveView, you've got one code base. There's no frontend/backend split, so you don't think about the API, you don't worry about going back and forth between JSON and all the associated error handling, you don't worry about versioning and keeping deployments in sync when/if you break APIs. You shouldn't really compare it to React, you should compare it to your whole stack, and see how a lot of the code and the worries just kind of go away. This is much like how it used to be with classic server-side rendered Rails/PHP/Phoenix... except with LiveView you can update part of the page running on the client, in response to events coming from the client without a page refresh.
- aczerepinski 7y agoEliminating a bunch of API code.