I know devs love seeing short opinionated videos about technology, but this should serve only to guide them as to why one technology is more productive and represents less career risks. As to really learn something, one should not see fast videos but read books, documentation and reference really really slowly and deeply.
@@moveonvillain1080 Knowing things best require time, investing time leads to money, thinking in short term does not make you earn any real money either. Ask yourself why computer scientists, infosec specialists and A.I. experts earn more than most JS developers, that's because studying more makes you enter the ranks of the few.
If you mention Recoil, you should mention Jotai, which is just Recoil but better in every single way (also an atomic based state management system, by the same people who made Zustand)
Great overview of React. I agree with most of it, except for the Redux case. I know it might sound old but redux is a staple lib and offers great functionality. I believe it is a must to learn it because a lot of actual production projects are using it. You wont always build shiny new website and often you do maintenance for previous website. In the recent years with redux toolkit, i believe the use of the lib got way easier. And even more with the integrated RTK query solution that provides a great experience for server data fetching. So i would advise any react dev to dive deeper in this lib !
@@archmad you cant just come to a project a just say "i'll refacto the entire 3 years old code base because i dont like the lib, it will take 2 full month and you wont get any visible benefit". Redux is here, if you want to be employable learn it, it's that simple
I get what you are saying. My main issue with redux is that over time you tend to add everything in stores. In recent years I always tend to use the easiest approach and use internal component state as much as possible. There are very few instances where I need information across the entire application (auth / theme / tokens) and that's where Context API or Recoil comes into play. Otherwise I'm modularising as much as possible and sticking to local state. I can see the appeal of Redux Toolkit tho.
@@Goyo_MGC local state is the key, if you have redux, stay with it, but moving forward, try to isolate things, let redux handle the really "global" ones, but then you'll realize you only have a handful of globals that you don't need redux at the end.
Maybe it's because I'm perhaps overly influenced by Theo, but I would recommend Wouter if you're doing non file based routing and Zustand for state management. Oh and I hate doing anything frontend without Tailwind CSS!
Thank you for this! This video is very timely. I'm currently going through Jonas Schmedtmann's new React course in Udemy (sharpening my React skills after being laid off), then I saw this video after watching your other video about SolidJS. Is it too late for me getting back to React? Should I focus on something else? Sorry, kinda lost.
Hey! Good question, and I'm glad you reached out. I cannot stress this enough: if you are looking for a job, React IS YOUR BEST BET. Libraries like SolidJS are nice and interesting, but their exposure on the job market is minimal. Solid / Svelte / Qwik are nice to haves, BUT all stats and metrics point to React being the most in demanded UI Library regardless of the sector.
that never ending argument of whether react is a lib or framework was caused by react. even now the react team still like calling it a library but the reason they call it a lib is marketing and sense of humor. if next js is a meta framework then react is obviously a framework. a meta framework is a framework of a framework. if react is a lib then next js is not a meta framework. another thing people just need to know the difference between a lib and a framework. just because react calls it a lib doesn't make it a lib.
from someone who doesn’t know much about react- a lib is a library of classes/components, whereas a framework is usually more involved in that it will take over things that you would have to do yourself in the vanilla world like rerenders
Thank you! The numbers suggest otherwise. This video is performing worse than the previous 10 I posted. People are not clicking on React content anymore 😅
can u compare recoil to zustand? also a lot of people said react-query replaced their need for state management, if u could mention why that is as well
Are you using vim bindings in webstirm i think it's is or is the thick cursor there for no reason at all ? Great video as always ( wow this line is getting old I'll try to come up with something better next time 😁 )
shadcn is making radix + tailwnd easy to use , and zustand fo global state , it's light weight and can ramp up to redux complexity if needed , it also has some cool plugins , tanstack router is the new kid on the block and my boy tanner doesn't miss , he even has plans to turn it into a meta framework
So I created a simple CRUD application with a tiny sprinkle of custom validation for the create/edit form. Now when I type on the keyboard, the field frequently loses focus and UX is actually terrible. (it would work fine if I could put whole logic in a single big file, but I wanted to have reusable component) Am I just unlucky or is it considered a common flaw in React?
Without knowing the exact code, it sound like your component is remounting the input to the dom every time you are typing. When the input is recreated, it looses focus. It's not a common issue, not a React bug - I would guess it's some sort of problem caused by the way you wrote that component.
Hateful comment about react: 1. The only reason it's popular is because of the community which has been there for a long time since react came before the better js frameworks . 2. Vue, Svelte and Solid are simply better, more intuitive and get the job done faster in cases where community support doesn't matter a lot. 3. It's owned by Meta
What about @tanstack/router ?????? I expected it to be recommended router for react 😢 And what about tailwind instead of css modules? 😭😭😭 I’m really disappointed with your preferred stack for such things but love your channel anyway, already watching even more than Fireship, thanks for the good content
Hey! I know the tanstack libs are gaining a lot of popularity and momentum, but I felt it was more appropriate to give React Router a shoutout since it has such a long history in the ecosystem. Tailwind is a good option (I have a few videos on this topic on the channel), but it is rather opinionated. Since this was a "React review" I believed it would be more useful to stick with the basics that are doing the job good enough. Haha thank you for the kind words! I really appreciate it!
![React Course - Beginner's Tutorial for React JavaScript Library [2022]](http://i.ytimg.com/vi/bMknfKXIFA8/mqdefault.jpg)
![⭐ฮิตในTikTok!! ( หมูเด้ง MooDeng ) Ver. แดนซ์โจ๊ะๆ ReMix BY [ ดีเจกิต รีมิกซ์ ]](http://i.ytimg.com/vi/3krsyfWUeHU/mqdefault.jpg)
I know devs love seeing short opinionated videos about technology, but this should serve only to guide them as to why one technology is more productive and represents less career risks. As to really learn something, one should not see fast videos but read books, documentation and reference really really slowly and deeply.
Would love to do that..... If only it would increase my bank balance at the end of every month
@@moveonvillain1080 Knowing things best require time, investing time leads to money, thinking in short term does not make you earn any real money either. Ask yourself why computer scientists, infosec specialists and A.I. experts earn more than most JS developers, that's because studying more makes you enter the ranks of the few.
If you mention Recoil, you should mention Jotai, which is just Recoil but better in every single way (also an atomic based state management system, by the same people who made Zustand)
I just love Zustand. So easy to setup.
What's about jotai
Great overview of React. I agree with most of it, except for the Redux case. I know it might sound old but redux is a staple lib and offers great functionality. I believe it is a must to learn it because a lot of actual production projects are using it. You wont always build shiny new website and often you do maintenance for previous website. In the recent years with redux toolkit, i believe the use of the lib got way easier. And even more with the integrated RTK query solution that provides a great experience for server data fetching. So i would advise any react dev to dive deeper in this lib !
nope, context is enough or react-query
@@archmad you cant just come to a project a just say "i'll refacto the entire 3 years old code base because i dont like the lib, it will take 2 full month and you wont get any visible benefit". Redux is here, if you want to be employable learn it, it's that simple
I get what you are saying. My main issue with redux is that over time you tend to add everything in stores. In recent years I always tend to use the easiest approach and use internal component state as much as possible. There are very few instances where I need information across the entire application (auth / theme / tokens) and that's where Context API or Recoil comes into play. Otherwise I'm modularising as much as possible and sticking to local state. I can see the appeal of Redux Toolkit tho.
@@Goyo_MGC local state is the key, if you have redux, stay with it, but moving forward, try to isolate things, let redux handle the really "global" ones, but then you'll realize you only have a handful of globals that you don't need redux at the end.
@@archmad I would say it depends on your application. But i agree that if not necessary try to avoid redux. But still it's great to know how it works
Maybe it's because I'm perhaps overly influenced by Theo, but I would recommend Wouter if you're doing non file based routing and Zustand for state management. Oh and I hate doing anything frontend without Tailwind CSS!
Thank you for the suggestions!
Thank you for this! This video is very timely. I'm currently going through Jonas Schmedtmann's new React course in Udemy (sharpening my React skills after being laid off), then I saw this video after watching your other video about SolidJS. Is it too late for me getting back to React? Should I focus on something else? Sorry, kinda lost.
Hey! Good question, and I'm glad you reached out.
I cannot stress this enough: if you are looking for a job, React IS YOUR BEST BET.
Libraries like SolidJS are nice and interesting, but their exposure on the job market is minimal.
Solid / Svelte / Qwik are nice to haves, BUT all stats and metrics point to React being the most in demanded UI Library regardless of the sector.
that never ending argument of whether react is a lib or framework was caused by react. even now the react team still like calling it a library but the reason they call it a lib is marketing and sense of humor. if next js is a meta framework then react is obviously a framework. a meta framework is a framework of a framework. if react is a lib then next js is not a meta framework. another thing people just need to know the difference between a lib and a framework. just because react calls it a lib doesn't make it a lib.
from someone who doesn’t know much about react- a lib is a library of classes/components, whereas a framework is usually more involved in that it will take over things that you would have to do yourself in the vanilla world like rerenders
Great video for a great technology 🎉❤ we love you (React)
Thank you!
The numbers suggest otherwise. This video is performing worse than the previous 10 I posted. People are not clicking on React content anymore 😅
can u compare recoil to zustand? also a lot of people said react-query replaced their need for state management, if u could mention why that is as well
Will do! Thank you for the suggestion!
awesome summary
Glad you think so! Thanks!
Are you using vim bindings in webstirm i think it's is or is the thick cursor there for no reason at all ?
Great video as always ( wow this line is getting old I'll try to come up with something better next time 😁 )
Thank you for the feedback! That's the cursor I usually work with - just got used to this style.
I have been using @preact/signals in a react project lately. it's pretty sweet. if you squint your eyes you are using solid.
Haha nice! Just don't look at the bundle size :D
shadcn is making radix + tailwnd easy to use , and zustand fo global state , it's light weight and can ramp up to redux complexity if needed , it also has some cool plugins , tanstack router is the new kid on the block and my boy tanner doesn't miss , he even has plans to turn it into a meta framework
Thanks for the great suggestions!
Great Video
Thank you!
So I created a simple CRUD application with a tiny sprinkle of custom validation for the create/edit form.
Now when I type on the keyboard, the field frequently loses focus and UX is actually terrible.
(it would work fine if I could put whole logic in a single big file, but I wanted to have reusable component)
Am I just unlucky or is it considered a common flaw in React?
Without knowing the exact code, it sound like your component is remounting the input to the dom every time you are typing.
When the input is recreated, it looses focus. It's not a common issue, not a React bug - I would guess it's some sort of problem caused by the way you wrote that component.
Vite does SSR too
20+ years ago we called this 'progressive enhancement'.
No idea if youtube will block this: en.wikipedia.org/wiki/Progressive_enhancement
Haha :))
Thanks
Do
"Everything you need to know about SolidJS"
Will do! Thanks for the suggestion!
first view😀
🎉
Hateful comment about react:
1. The only reason it's popular is because of the community which has been there for a long time since react came before the better js frameworks .
2. Vue, Svelte and Solid are simply better, more intuitive and get the job done faster in cases where community support doesn't matter a lot.
3. It's owned by Meta
Can't argue against any of your points - you are right.
Damn, facts.
huheueuheuhuhuehuhehuhe
~insert here hateful comment about React~
Outrageous opinion!
What about @tanstack/router ?????? I expected it to be recommended router for react 😢
And what about tailwind instead of css modules? 😭😭😭
I’m really disappointed with your preferred stack for such things but love your channel anyway, already watching even more than Fireship, thanks for the good content
Hey! I know the tanstack libs are gaining a lot of popularity and momentum, but I felt it was more appropriate to give React Router a shoutout since it has such a long history in the ecosystem.
Tailwind is a good option (I have a few videos on this topic on the channel), but it is rather opinionated. Since this was a "React review" I believed it would be more useful to stick with the basics that are doing the job good enough.
Haha thank you for the kind words! I really appreciate it!