harmon25
Happy holidays everyone, I feel like Christmas has come early!
Posted today by the React team:
Introducing Zero-Bundle-Size React Server Components – React Blog (reactjs.org)
This looks an awful lot like LiveView - especially when combined with Surface! (about 25 minutes into the video they demonstrate what is essentially a live_patch)
I have been experimenting with rewriting a React SPA(phoenix/gql backend) into something server rendered with LiveView + Surface, have the impression that this move by the React team helps validate that decision.
RFC: React Server Components by josephsavona · Pull Request #188 · reactjs/rfcs · GitHub
The first comment on the RFC ^ likens React Server Components to technologies like ASP.NET Blazor… Wonder if all the Facebook erlang work has been towards bringing React Server Components to the erlang/elixir ecosystem?
Big shout out to all the folks involved with Phoenix + LiveView ( +Surface) for setting this trend, or maybe seeing into the future ![]()
Thoughts?
Trending in Discussions
Other Trending Topics
Latest Phoenix Threads
Chat & Discussions>Discussions
Latest on Elixir Forum
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex










First 2 of 2 Posts
a8t
Yeah, as soon as I saw the React announcement, I headed over here to see if folks were already talking about it.
50kudos
What makes the React Server Components a bit cooler is interactive markup (that jsx) lives in the same tree for both client and server rendering. Client states are untouched. Their immediate format sent over the wire is smart enough to merge particular component from server into the client react tree.
Though I’m for backend solidarity
DHH on X: "Hotwire aka NEW MAGIC is finally here: An alternative approach to building modern web applications without using much JavaScript by sending HTML instead of JSON over the wire. This includes our brand-new Turbo framework and pairs with Stimulus 2.0 😍🎉🥂 https://t.co/Pa4EG8Av5E" / X