Love all the new updates except for the form hooks. React Query useMutation has a better api design. Destructuring assignment into object is so much better than an array. Only take out what is needed. Also was thinking about learning Next.js but with RSC in react 19, what advantage would I get?
To be fair you could just wrap useActionState and have it return an object, so you wouldn't need useMutation (unless you need things like onSuccess/onError/revalidation). Actually now that I wrote this out yeah I'd stick to React Query lol. And yeah with RSC in React 19 Next.js is becoming less and less attractive. I'd just stick to React + React Query or Remix tbh
Yea I've never been a fan of reacts usage of arrays for values and especially now where some things use objects others use arrays. Feels very inconsistent. Next does a lot of things very well and some not so well so it all comes down to what you would want to use it for. I do love how Next is always pushing React forward. It's currently the only place where you can (and have been able to for a while now) use server components and a lot of other react 19 features. They built some of the things based off of the canary version so now they're having to make some changes for the things that changed with the beta. Definitely give it a try, I love server components and how it cleans up so much code. Less loading states, less screen flashes etc. Let me know if you'd find a server components video valuable and I can try working on one 👀
@@cdbrw I found your video extremely helpful. For future videos I'd love to see comparison of similar performant applications like react 19 app using (React-query, tanstack-router) vs Next.js. I have a feeling tanstack-router prefetching for page data (if that page doesn't require seo ex: enterprise application dashboard) would be faster than Next just by design. Or maybe a svelte & next breakdown of individual api performances. (hint: svelte's api is significantly better than anyone else's last time i worked with it. I was able to moderate frame rates in the 100ths of a second vs 10s of a second with other frameworks). However, I don't think a break down in business case uses will be doable in a 10 min video though. The needs (both immediate and long term) projects are very different between an enterprise dashboard and an E-commerce website. Also, you would need years of experience and multiple different projects from different business - large, medium and small to pull this off. Anyhow, keep up the good work. I look forward to more of your videos. Happy coding ✌
![[Full] 4 ต่อ 4 Celebrity EP.920 | 3 พ.ย. 67 | one31](http://i.ytimg.com/vi/KwiW2M_kAg4/mqdefault.jpg)
really nice. keep it up!
🙏🙏
The only time i'm looking forward to a monday is when a new codebrew video drops
🥰
Also side note: the T’s in “Button” are not silent 😂😂😂
that's cool man 😎
Love all the new updates except for the form hooks. React Query useMutation has a better api design. Destructuring assignment into object is so much better than an array. Only take out what is needed. Also was thinking about learning Next.js but with RSC in react 19, what advantage would I get?
To be fair you could just wrap useActionState and have it return an object, so you wouldn't need useMutation (unless you need things like onSuccess/onError/revalidation). Actually now that I wrote this out yeah I'd stick to React Query lol. And yeah with RSC in React 19 Next.js is becoming less and less attractive. I'd just stick to React + React Query or Remix tbh
Yea I've never been a fan of reacts usage of arrays for values and especially now where some things use objects others use arrays. Feels very inconsistent.
Next does a lot of things very well and some not so well so it all comes down to what you would want to use it for. I do love how Next is always pushing React forward. It's currently the only place where you can (and have been able to for a while now) use server components and a lot of other react 19 features. They built some of the things based off of the canary version so now they're having to make some changes for the things that changed with the beta. Definitely give it a try, I love server components and how it cleans up so much code. Less loading states, less screen flashes etc. Let me know if you'd find a server components video valuable and I can try working on one 👀
@@cdbrw I found your video extremely helpful. For future videos I'd love to see comparison of similar performant applications like react 19 app using (React-query, tanstack-router) vs Next.js. I have a feeling tanstack-router prefetching for page data (if that page doesn't require seo ex: enterprise application dashboard) would be faster than Next just by design. Or maybe a svelte & next breakdown of individual api performances. (hint: svelte's api is significantly better than anyone else's last time i worked with it. I was able to moderate frame rates in the 100ths of a second vs 10s of a second with other frameworks). However, I don't think a break down in business case uses will be doable in a 10 min video though. The needs (both immediate and long term) projects are very different between an enterprise dashboard and an E-commerce website. Also, you would need years of experience and multiple different projects from different business - large, medium and small to pull this off. Anyhow, keep up the good work. I look forward to more of your videos. Happy coding ✌