laiboonh
Hi all,
I am trying to convince my team to use liveview over the current react. What are some of the points where one should consider using liveview instead of react?
To start off:
- Using one language to code frontend and back saves us from context switching
- Arguably easier to do as there will no need for data serialising and de-seriialising or REST
- …
Where Next?
Trending in Discussions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Producing high quality Elixir screencasts since 2017.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
egze
What’s in it for you? Why are you trying to convince them?
Curious to hear more of your own arguments. (Not saying it’s a bad initiative, but trying to make you express your own reasons, and not the forums)
kanishka
I am new to liveview, familiar with elm, rescript-react, angular, and various ssr solutions before SPA’s came around.
I am trying to figure out if there are operational downsides to using liveview, since it sounds like liveview changes you from running a mostly stateless backend to a stateful backend? Do you have to put more effort into horizontal scaling and thinking about node fail over?
laiboonh
Mainly because i am allergic to javascript.
kanishka
Elm is great fun, if js is your only objection, but I love the simplicity of server side, no API
laiboonh
Im a fan of elm as well. Keep a look out for this GitHub - gren-lang/compiler: Compiler for the Gren programming language · GitHub.
cblavier
If you’re fond of automated testing, you can argue that it is way easier to test Liveview code than React.
mindok
Have you read the history lesson on why liveview came to be? You may get some answers there.
tj0
That’s a pretty long article, but there’s probably 1000 words on phoenix liveview performance, maintainability, etc.. but at the end of the day it really depends on your application.
tfwright
For me the biggest advantage is keeping all data management in one place. With a react front end, you basically have 2 applications, and each requires its own set of patterns, tests, etc to deal with state. In comparison with just react (it is of course possible, arguably necessary, to leverage other libs to help) live view is a lot more equipped to do this in a robust, reliable way.
In my experience, unless you have absolute top of the line expert react devs, you are looking at 3 or 4 or even more times as much dev time.
I guess this falls under “no need for API” but i feel that formulation drastically undersells the advantage.
DevotionGeo
It’s a nice post by Chris McCord!
LiveView is a very big thing in Web Development history. We need to have a documentary live the Elixir Documentary.