Do I need to run Next to get server-side React, or can I get the functionality in regular Express or something similar and import server-side React as library?
Really depends on your users’ needs. I won’t be adding ssr for our app any time soon. We keep out marketing material separated from our users’ applications. seo just isn’t required for a web app when it is complimentary to your product, not the product itself. And so I agree that ssr just for the sake of it is just throwing $$$ in the wind. (just saying the choice is not just binary in either direction) ¯\_(ツ)_/¯
@@_kostant Yea.. most people overindex on time to render for SEO even though it barely matters .. not as much as authority .. optimizing SSR workflows is the biggest joke on the web world now
I wasn't around yet in the front-end world when the whole Class Components -> React Hooks transition started. How would you gauge the change in mental model then versus now? As in, I heard people were pretty resistant to the change back then; but nearly no-one would go back to Class Components nowadays. Do you see the same thing happening?
@@Igstefano it was messy but to be honest React’s class components were written in a clunky way, because method calls as event handlers had to be either called in a throwaway arrow function or bound to the `this` context of the class in the constructor. And state management was sort of bolted on. So functions + hooks were simpler after an adjustment period. But some people were pretty annoyed and went to Vue (then got mad when Vue adopted the composition API and then they came back to React) or Svelte (which had a barebones ecosystem at the time). This also coincided with when Redux and MobX were falling out of fashion and alternatives like Zustand and atoms/jotai became more popular, more people were using immer, and then swr and more importantly React Query became popular later and by that point the ecosystem was unrecognisable. So it wasn’t just class > funcs but also redux > anything but redux at the same time. The gradual transition helped a lot though.
@@psychoedge agreed, it isn't a huge difference. It is, though, big enough to generate resistance, as all change does. My question was more about if it's following a historical pattern or not.
React 19 does not control your server or something like that. React is a library, not a framework. As such, it only controls stuff over which React as agency: modules that export components, modules marked with directives, and modules that export Server Functions. For anything else, you're on your own, and you'll see the errors and the security issues in production soon enough.
OK legends, can someone tell me the best tech stack to get right. I see crazy updates from tailwind, gsap and now react. What are the exact versions that would lead to the optimal building of a frontend platform? I'm perfectly fine finetuning an LLM to the notation of the new libraries. Just eager for some opinions!
"React 19 is here but nobody can upgrade as all the dependencies will take another year to catch up" It's not true. Do you guys code react? If you use NextJS or Waku or any React framework, it already used React 19 RC for a while. So react 19 stable version rolled out is not a big change.
@@yojou3695 Ah, yes, I use Remix and React Router as well. Vite 6 has already been released with an environment API, which Remix and React Router need to implement RSC. So, I think it will not take too much time for Remix/React Router.
Module federation was always 1) a bundler feature, and 2) a client-side feature. In theory, if you stick to client-side components, you should still be able to do module federation the same way it worked in older versions of React. If you want the client/server weave via RSC, I haven't seen any existing solutions yet. You'd want some client-side runtime that's able to stream in server-rendered JSX and bootstrap it from multiple decomposed React servers, or, perhaps have your app shell React server merge streams from multiple sources on the server somehow. Theoretically possible, but not sure if anyone's gotten this working yet.
we really know nextjs , but still it sucks, the worst thing is we cannot share the data across pages , like fetching at one place , and we have to do alot of things for it, like you have mentioned .
I don't know - as somebody who loves transparency, I'm not a fan of what the compiler does. Obscuring what's happening doesn't make for great maintainability in my opinion. And given the overhead introduced by memoization, I'm skeptical how often React gets it right. Because without actually running the code or at least using AI, I can't envision how they would be able to reasonably accurately determine what needs to be memoized.
I`m working with NEXT JS for a company and i wish everyday i can uninstall it but its to bloated (api, pages, translations, etc) that i have to work with this s**t until i change the company :(
I can see your point. NGL I like it though. I think it’s exciting still though. Who wants to do the same thing again and again. I started in the WP/jQuery days and no thx haha
Seriously WTF, Svelte is the one who popularized the Compiler approach and these React people made fun of it and here we are now with a React Compiler, LMAO 🤣
I have to wait till React 20 so that all the dependencies upgrade to react 19
This, or you start contributing with PRs. That would help everybody, including you.
This, or you start contributing with PRs. That would help everybody, including you.
React 19 is here but nobody can upgrade as all the dependencies will take another year to catch up
True
hahah
Haha agreed, but I think some of the dependencies that work for nextjs could work with react19 because of the server component architecture
my app fucked up when is upgraded to react 19
Just upgraded at work today, no issues 👍
Welllllll shit. I still haven't finished upgrading all my company projects to react 18.
Man, feel like I'm circling a black hole sometimes.
Diffs for hydration errors!
DIFFS FOR HYDRATION ERRORS!
about time
Migrated and some of my refs stopped working without any errors or warning
Typical React
How?
@@lessko9 Probably how you pass refs in react 19
This guy knows how to make engaging ads
bolt is actually really nice, I have used it multiple times to start a project, then export it and continue with cursor or windsurf
Would be cool if it could detect hydration errors caused by chrome extensions
it can. ColorZilla Chrome extension causes one.
@ yeah I mean if it could tell you that the hydration error is coming from the extension and not from your app
Fun stream. Had to watch the video to refresh my memory though. Thanks Theo!
Do I need to run Next to get server-side React, or can I get the functionality in regular Express or something similar and import server-side React as library?
Why they did not mention anything about React compiler when React 19 was released few days ago ?
Yeah, as I remember they planned to release the compiler in this version 🤔
It is unstable and released as a babel plugin "bable-plugin-react-compiler"
it's beta and has been decoupled from react 19, now is a babel plugin
hi - compiler demo is awesome 22:41, do you have demo code shared publicly ..?
rendering content on server vs client ads $$$ for your apps. client rendering is free. server rendering costs a lot
Except you need to do ssr for seo reasons, so you end up doing both.. :D
Really depends on your users’ needs. I won’t be adding ssr for our app any time soon. We keep out marketing material separated from our users’ applications. seo just isn’t required for a web app when it is complimentary to your product, not the product itself. And so I agree that ssr just for the sake of it is just throwing $$$ in the wind.
(just saying the choice is not just binary in either direction)
¯\_(ツ)_/¯
@@miran248 time to first whatever is not that important for SEO.
@@_kostant Yea.. most people overindex on time to render for SEO even though it barely matters .. not as much as authority .. optimizing SSR workflows is the biggest joke on the web world now
the wait is over
I wasn't around yet in the front-end world when the whole Class Components -> React Hooks transition started. How would you gauge the change in mental model then versus now? As in, I heard people were pretty resistant to the change back then; but nearly no-one would go back to Class Components nowadays. Do you see the same thing happening?
100%. In frontend if you refuse to follow the trend you fall quick
@@Igstefano it was messy but to be honest React’s class components were written in a clunky way, because method calls as event handlers had to be either called in a throwaway arrow function or bound to the `this` context of the class in the constructor. And state management was sort of bolted on. So functions + hooks were simpler after an adjustment period. But some people were pretty annoyed and went to Vue (then got mad when Vue adopted the composition API and then they came back to React) or Svelte (which had a barebones ecosystem at the time).
This also coincided with when Redux and MobX were falling out of fashion and alternatives like Zustand and atoms/jotai became more popular, more people were using immer, and then swr and more importantly React Query became popular later and by that point the ecosystem was unrecognisable. So it wasn’t just class > funcs but also redux > anything but redux at the same time.
The gradual transition helped a lot though.
The difference isn't as huge as you think. Most components can be rewritten fairly quick. Even Vue now offers a hook-style API and I enjoyed it a lot.
@@psychoedge agreed, it isn't a huge difference. It is, though, big enough to generate resistance, as all change does. My question was more about if it's following a historical pattern or not.
React 19 does not control your server or something like that. React is a library, not a framework. As such, it only controls stuff over which React as agency: modules that export components, modules marked with directives, and modules that export Server Functions. For anything else, you're on your own, and you'll see the errors and the security issues in production soon enough.
Thanks!
🙏
OK legends, can someone tell me the best tech stack to get right. I see crazy updates from tailwind, gsap and now react. What are the exact versions that would lead to the optimal building of a frontend platform? I'm perfectly fine finetuning an LLM to the notation of the new libraries. Just eager for some opinions!
Oh wow, the Taxi company released a product for Devs
if something is not intuitive it’s generally not a good idea
my
Right but when Nextjs performant dev server?
But inaccessible and it is not working when I tried to install it with npx create-react-app
Someone went and said the static part out loud.
"React 19 is here but nobody can upgrade as all the dependencies will take another year to catch up" It's not true.
Do you guys code react? If you use NextJS or Waku or any React framework, it already used React 19 RC for a while. So react 19 stable version rolled out is not a big change.
a lot of people do not use next and definitely not waku. Most projects are just vite (or even worse webpack) + react router + react
@@yojou3695 Ah, yes, I use Remix and React Router as well. Vite 6 has already been released with an environment API, which Remix and React Router need to implement RSC. So, I think it will not take too much time for Remix/React Router.
the video i was waiting for
Which draw editor you use in the video?
It's Excalidraw! :)
Hey @t3dotgg 🙂, could you please tell us how to store secrets like API KEYS in React? Unfortunately these are visible in a source code of the app
🙏
amazing video
What’s your theme in cursor?
poimandres
So does this kill Module-Federation?
Module federation was always 1) a bundler feature, and 2) a client-side feature. In theory, if you stick to client-side components, you should still be able to do module federation the same way it worked in older versions of React. If you want the client/server weave via RSC, I haven't seen any existing solutions yet. You'd want some client-side runtime that's able to stream in server-rendered JSX and bootstrap it from multiple decomposed React servers, or, perhaps have your app shell React server merge streams from multiple sources on the server somehow. Theoretically possible, but not sure if anyone's gotten this working yet.
Theo over-dramatising the premise in the first 20 seconds of the video as per usual. Actually, dramatising everything. Bro, it's just the web
we really know nextjs , but still it sucks,
the worst thing is we cannot share the data across pages , like fetching at one place ,
and we have to do alot of things for it, like you have mentioned .
Astro 🚀all the way baby!
I don't know - as somebody who loves transparency, I'm not a fan of what the compiler does. Obscuring what's happening doesn't make for great maintainability in my opinion.
And given the overhead introduced by memoization, I'm skeptical how often React gets it right. Because without actually running the code or at least using AI, I can't envision how they would be able to reasonably accurately determine what needs to be memoized.
React needs some schedule for realeses like angular.
I`m working with NEXT JS for a company and i wish everyday i can uninstall it but its to bloated (api, pages, translations, etc) that i have to work with this s**t until i change the company :(
Finally I can use React 18 and upgrade to 19 next year😂
upgrade existing apps to React 19 will be painful but worth it
another youtuber forked bolt to support using whatever ai model you want including local ones, instead of claude
This like is for bolt. Sorry theo, before you could get one the add got in the way 😂😂
Not even a minute in and already trying to sell me crap
Well It still make your browser consume 3GB of your PC memory, right ?
JS on the client is never the reason your browser consumes such high amounts of ram, it's just the browser itself
@@uspecl nah it's mostly bad React devs
It's mostly that s take up lot of memory
does it mean we can ditch the ridiculous nextjs from now on? 😂
quack
19 views nice
19 comments now
That means you're 20th viewer
What's another way to say first without saying first while being just as vapid 🤔
I swear it was on 5678 when I read it, but not as of writing a few seconds later.
no its not stable, npx-create-react app is till having a stroke
Gj
And yet, I’m even more convinced that react use case is even smaller, for the majority of apps and pages doesn’t (and shouldn’t) use react.
It’s so tiresome
I can see your point. NGL I like it though. I think it’s exciting still though. Who wants to do the same thing again and again. I started in the WP/jQuery days and no thx haha
19 likes
Bro fell off
yeah i respected bold 1. it's open source 2. it will make future programmers always juniors
Love the jacket 👍
I feel like these changes do not bustify two years of waiting leave alone a major release
wher compiler
The only good thing is avoiding Nextjs
WHY AM I SO EARLY
because no one cares about React junk
First
Seriously WTF, Svelte is the one who popularized the Compiler approach and these React people made fun of it and here we are now with a React Compiler, LMAO 🤣
Still its a library not a framework like Next.js who offers caching, routing, middleware and many more things out of the box.
The most useless video en react 19 yet
:O
So many new useless things… react become the tech front end with the worse learning curve every year.
how
react is becoming like php
how much shit talking people do about some minor bug fixes and improvements... ohh react 19 looks willd 😒🥱
But like... did bolt pay you to talk about their paid tool ...? 🥲😄😭
First