React Is A Backend Framework Now
Вставка
- Опубліковано 5 бер 2023
- The future of React is scary, but it's starting to click for me. Thank you Dan for getting me excited about React again 🙏
LINK TO DAN'S TWEET: / 1631887155080429569
ALL MY VIDEOS ARE POSTED EARLY ON PATREON / t3dotgg
Everything else (Twitch, Twitter, Discord & my blog): t3.gg/links
A lot of y'all seem to think the SQL example runs on the client? It doesn't. The ENTIRE point of this is that React Server Components ONLY run on the server. That's the cool part!!!
Welcome to PHP! and congratulations on a decade long journey around tech universe
Never thought PHP would make such a comeback, nice!
2003: Writing SQL inside PHP.. this is a 💩
Well done JavaScript guys. You are like on 90% progress to discover that weird server side thing called PHP.
after "HTML in JS" and "CSS in JS", React now presents you: "SQL in JS"!
I swear these tech stacks evolve so fast by the time you install a package it’s legacy
You still need an API for multiple consumers or frontends and you still need an Application layer if you want consistency.
PHP kind of already has this pattern with Livewire. Typically the server renders the big moving parts and the client handles the real time stuff.
In some ways, this feels like a return to early ASPNET.
"We might not need APIs anymore" , this words come only from a person who don't know why we build APIs, mostly a frontend developer who don't know backend but try to build backend, all these shortcuts that people talk about having backend code in frontend library or through your APIs and Relational Database and use firebase instead for everything, they are just shortcuts to build small things and they will never scale well with you, all these technologies exists to be part of your architecture and take benefits from them when they make sense, not to totally replace your architecture
I think the ability to fetch data from anywhere with Server Components is cool, but that also seems to present some challenges when it comes to code clarity and optimization. The paradigm used by Remix and Next of fetching data at the route level means that it’s much easier to track down slow requests and duplicate calls. If you can make requests in any component and have multiple developers working on a project without a standard convention, things get messy - it just becomes the same problem we had with CSR. Also, side note, the more I see examples of Server Components the more I feel they create a sort of Russion Doll effect for our components, One might have Post for the actual component, but need PostWrapper for loading data, PostSuspense for adding a loading state to any client side rerequests, etc. Feels like the Container Presenter model but worse.
This is cool! I need to play with this myself to understand it better, but I really like the way React is going with these server components! Thx Theo <3
I remember hating Adobe Cold Fusion because there was no separation between the backend and front end.
One of the things I like about t3 app is that it gives you a guide on how to implement key technologies together. Really looking forward to seeing how the t3 stack will guide/recommend how to use server components.
How is this different from PHP returning html file to the client ?
The more I watch this channel the more I tend to think that Theo is just a pro at making good looking complicated react tutorials that only work for basic stuff / non sensitive apps.
I feel like the structure in React will be the biggest thing holding stuff like this back.
This is spaghetti PHP code!
Awesome video 🔥 definitely exciting times to be a react/next developer. I agree with you, once it all clicks in your brain it’s so much fun!