The best way to learn the value of a solution is to experience what the problem is first. A lot of what I appreciate about Solid and Svelte comes from experience in the parts of React that I have found to be less than ideal. Also a lot of the issues that React has - and the ecosystem that has built around it to make it so great - has informed the features that come out of the box in other solutions. For example comparing data fetching in Solid Start with React Query. So yeah if I was starting now I would definitely still go in on React - there's so much great learning material out there!
@@frankyb702 I know your joking but you can learn a bunch of things from asp, I thought you were going to talk about using shockwave. Maybe some coldfusion.
Yeah true, it cannot just die over night. Take jQuery for example. We all love to say jQuery is dead while we work with our shiny new frameworks and libraries, but looking at NPM, jQuery still has 5 million downloads per week and that's not even counting all websites that use jQuery through a script tag from a CDN. Although I wouldn't recommend using jQuery for a new project since it's not really required these days, it looks like it's still a really valuable tool for many people.
@@rand0mtv660 but nobody ask the question is it too late to learn jQuery. No it is not too late, but it is just not needed unless it is really needed.. I am just wondering when folks get those hooks and memoe-ing those callbacks enough... React became kind a new jQuery as soon as they decided to recommend render-driven stateless function way to do things. React simply doesn't deliver its job well as a platform (though it wasn't intended to be a platform at first place), because it is not hiding the details of implementation well enough. It was intended to be a library.
This is sums up exactly how I feel too. React is a must learn for anyone wanting to break into front end development, and it’ll exist in codebases for at least a decade even if other frameworks become more popular
I'm one of those people hired w/o any prior react experience. I was primarily vue developer, but applied for React role that required 3 years of commercial experience with React, and I somehow managed to get that position :D It was exactly 9 months ago, today I was promoted to senior position (I'm not joking lol) :D
I recently jumped into web dev from desktop and picked up react within a week, within 2 weeks it was obvious that solid was the much better tech, jumped onto that and now well on the way with my project.
Couldn’t agree more. I’ve been learning fundamental web dev stuff (html, css, js) for about a year now. Recently started going deeper into learning react and the beta docs are tremendous
React is to web dev what Postgres is to databases. The fact that it has been around for so long created a wealth of resources to learn the tech, to debug potential issues, of talks/blog posts to learn the up and down of the technologies. And I didn't even mention the ecosystem. It is becoming more and more suprise-less, and that is a good thing I think. But idk man dude, I'm doing backend anyway so who am I ?
I been assigned to a legacy project that use react version 14 and the code are alien to me due the class component, no 'use' hooks, tech lead wont let me restructure the code base & dont even start with the state management. So is it worth it? Yes & agree 100% with Theo 👍
after fiddling with laravel, I've gone learning react with my existing js knowledge and had a great experience while using it with MUI for a simple CRUD app
No, it's not too late to learn React, but it's better to take a step back and understand the difference between client side, server side rendering and when you need it. People have been overengineering simple blog sites, not understanding that an SPA is not what will help them achieve what they want. I resort to Jinja with Flask for SSR most of the time because a React.js SPA will overcomplicate things. MERN, MEAN, MEVN - these buzzwords make budding devs blindly use frontend libraries and create SPAs that would be simpler to accomplish with SSR
I started to learn Svelte, they have a good tutorial on their website, but I began to understand why the framework is needed and how to use it properly only after I began to learn React.
Vacancies I see locally demand well-known tech. React, Webpack, MySQL etc. Even jQuery is still around. The only "new" thing that's getting listed on a lot of vacancies is Vue.
100% this. I'm about to introduce a React junior dev to Svelte, and I know he's going to have a huge jump start. Learning React leveled my skills up a ton back in the day. React is hard mode. If you can hang with React, then Vue, Svelte, Solid, and anything that comes next will be much much easier.
I started learning it this week. Not new to web development. I just took a long break. I remember when XHTML started replacing HTML 4. Most pages had table layout.
@@headlights-go-up ok sure? Nothing in react is really similar to svelte in terms of how you implement those systems so other than the fact that they use js.. they aren't really teaching you anything extra. You're still going to have to go through the svelte docs for most things you're wanting to do because react doesn't do it the same?
When I became a Vue expert, almost all the best practices in Vue applied to React and Angular. Now a days, all 3 frameworks do the same thing, they just emphasis on different aspects of coding. Just learn the different popular code packages and key words.
Even after something like Qwik or Svelte supersedes React in the “cutting-edge” space (I honestly feel like Qwik is gonna be the one to do this), there’s still gonna be legacy React codebases for years after this happens. Big companies aren’t moving to “cutting-edge” tech anytime soon.
You're right, learn your lessons, folks. Driving components by rendering cycle and trying to hide state with magic hooks bound with some naming conventions is a bad idea, that is a lesson. And it is time to forget about React, there is a ton frameworks which are doing better job to hide complexity of implementation and which are allowing to structure the code better.
react has pros and cons, i learn one and be able to understand so many other derivative framework is nice. however a lot of companies aren't this advanced as they are not usually frontend focused then react wouldn't appear as important since they can't move on
It's so dominant that there will be react work for decades to come. Sure qwik, solid etc are impressive but they aren't going to take over the way react did. Bigger than the tech itself is the community, support and ecosystem around it.
The way I see is that become expert in one SPA framework like React, Angular, and Vue. Then transitioning to others are much easier to learn. At the end all these are tools to solve a need. I don’t think any of these tools are vastly better than other… assuming they all use TS. I just hope browser would one day run TS naively…..
As much as I enjoy Qwik/SolidStart right now to play around in the ecosystem, for prod I'm still React. It'll be a while and some maturity until I feel I'll be confident enough to get where I am with React. I never enjoyed vue/svelte, and kept off that hype-train, and feel it was the right decision. Qwik/Solid with vanilla-extract I am liking though. Still hate tailwind.
There will be piles of react code to maintain for decades to come. There's still companies running Perl from the 90's. If you're happy with maintaining legacy spaghetti code written in a forgotten tongue, you'll def. make a decent living.
Not Theo, but I don't think so. The beta React docs that he mentioned strongly recommends functional over class components, and most new React learning materials I've read/seen ever since I started learning (~10 months ago) are using functional components over classes
The reality is React is not going anywhere. It has become the standard for Web Apps. Only if the whole industry switches then we'd start worrying about it and with Vercel spearheading Next.js, there's no better time to start diving into React.
I stopped learning. I realized that for the data intensive crud apps I create Angular does the job just fine because speed and loading time are not of such a big importance. And the speed is more than okay anyway. Each time they mention a framework feature they should mention what type of webapps it targets.
@@paulholsters7932 I jumped onto SvelteKit which is amazing, coming from a python/django background, I find svelte very nice to work with. Never used Angular before.
chatGPT + React DOC = Easy $$$ chatGPT will help to explain functions or even comment over your provided code. I would say... teacher who want's to help :))
Been learning React.js for 2 years!! building projects upon projects using available APIs and building my own. I want to move to Next.js at some point this years thanks to some of your videos ! :) excellent work :)! I'm avoiding tutorial videos and just building through my understanding of the documentation, is this ok? Or best practices can be learned through sitting 30 min watching a guy building an app from scratch ? dream is to get a job as a junior one day!
@@MyPhuckDub I haven't really applied to jobs man. I initially started because I thought it was fun. This year though, I want to move to development and get senior in react. I'm in tech but Im seeing myself coding most of the time. Hopefully soon I can do this.. difficult to find entry level react roles y London, very competitive
I have always view react as an overcomplicated framework and i pick for me and the software we develope Vue or Svelte. Ofc this is opinion based, but they are just so more elegant and easier to use. React just seems like ugly tech
React is not enjoyable neither is Gatsby. I like the things you can do with Gatsby but just lord I hate using it. I sad you pretty much have to do React to get a job.
I dislike all these types of frameworks, there is so much boilerplate crap in the setup. I get it for large projects, there is no way around it, but for smaller ones... I see some "tutorial folks" spending hours with their tutorials for a simple hello world, stuff you could've written in vanilla js with some css in 10 minutes. There is a lot of "laziness" to these frameworks, package for this, component for that and panic when there is no package/component. I use alpinejs/vimesh-ui (for components) and tailwind JIT all via CDN's. A single exclamation mark in vs code and I can start, love it.
Thing is Theo, the frontend is still kinda Far-West-y. New frameworks come, new ideas come to frution, mindsets change, paradigms shift. Additionally, no tech rules forever, or at least commands a significant market share. So, the "there will be jobs in React for decades" sounds kinda biased. Remember when Angular was all the rage, when people only said they knew "MEAN" without even knowing what half of the Javascript they wrote does? Where are these stacks now?
The best way to learn the value of a solution is to experience what the problem is first.
A lot of what I appreciate about Solid and Svelte comes from experience in the parts of React that I have found to be less than ideal. Also a lot of the issues that React has - and the ecosystem that has built around it to make it so great - has informed the features that come out of the box in other solutions. For example comparing data fetching in Solid Start with React Query.
So yeah if I was starting now I would definitely still go in on React - there's so much great learning material out there!
It's never too late to learn React 🚀
Im still learning classic asp using vbscript. And then my goal is actionscript so i can make cool flash websites
I let chapgpt teach me
@@frankyb702 I know your joking but you can learn a bunch of things from asp, I thought you were going to talk about using shockwave. Maybe some coldfusion.
So happy this isn't some silly "React is dying!" video while still keeping an open mind.
You don't just stop ten years of momentum out of nowhere.
Yeah true, it cannot just die over night. Take jQuery for example. We all love to say jQuery is dead while we work with our shiny new frameworks and libraries, but looking at NPM, jQuery still has 5 million downloads per week and that's not even counting all websites that use jQuery through a script tag from a CDN. Although I wouldn't recommend using jQuery for a new project since it's not really required these days, it looks like it's still a really valuable tool for many people.
now the momentum will be going until the definitive death, until there react will be the new php
@@rand0mtv660 but nobody ask the question is it too late to learn jQuery. No it is not too late, but it is just not needed unless it is really needed.. I am just wondering when folks get those hooks and memoe-ing those callbacks enough... React became kind a new jQuery as soon as they decided to recommend render-driven stateless function way to do things. React simply doesn't deliver its job well as a platform (though it wasn't intended to be a platform at first place), because it is not hiding the details of implementation well enough. It was intended to be a library.
Yo bro, remembers someone saying PHP is dead 10 years ago, but still there's a lot of demand for PHP developers out there.
This is sums up exactly how I feel too. React is a must learn for anyone wanting to break into front end development, and it’ll exist in codebases for at least a decade even if other frameworks become more popular
jQuery still exists in a lot of code bases, and for sure when react dies it will still be in similar position.
@@katech6020 yeah exactly, knowledge of react will be useful for a long time
Like Fireship said in his recent video: Learn react if you want to get a job, learn Vue or Svelte if you want to enjoy what you are doing.
I'm one of those people hired w/o any prior react experience. I was primarily vue developer, but applied for React role that required 3 years of commercial experience with React, and I somehow managed to get that position :D It was exactly 9 months ago, today I was promoted to senior position (I'm not joking lol) :D
How lol? I am very curious about how you get the job.
@@phucnguyen0110 same. How in the world would they be okay with that?
Was it tough to handle the tasks that they assigned to you? Don't you got scared of getting fired?
I recently jumped into web dev from desktop and picked up react within a week, within 2 weeks it was obvious that solid was the much better tech, jumped onto that and now well on the way with my project.
these thumbnails are crazy. W video as always.
Couldn’t agree more. I’ve been learning fundamental web dev stuff (html, css, js) for about a year now. Recently started going deeper into learning react and the beta docs are tremendous
React is here for the long run!
It's never too late. I love your videos, Theo!!
I am currently learning react and loving it so far 😅
React is to web dev what Postgres is to databases. The fact that it has been around for so long created a wealth of resources to learn the tech, to debug potential issues, of talks/blog posts to learn the up and down of the technologies. And I didn't even mention the ecosystem. It is becoming more and more suprise-less, and that is a good thing I think.
But idk man dude, I'm doing backend anyway so who am I ?
Love the new doc's they are top tier
I been assigned to a legacy project that use react version 14 and the code are alien to me due the class component, no 'use' hooks, tech lead wont let me restructure the code base & dont even start with the state management.
So is it worth it?
Yes & agree 100% with Theo 👍
The "read more" on this clickbaited me so hard, good stuff 🙏
after fiddling with laravel, I've gone learning react with my existing js knowledge and had a great experience while using it with MUI for a simple CRUD app
No, it's not too late to learn React, but it's better to take a step back and understand the difference between client side, server side rendering and when you need it.
People have been overengineering simple blog sites, not understanding that an SPA is not what will help them achieve what they want.
I resort to Jinja with Flask for SSR most of the time because a React.js SPA will overcomplicate things.
MERN, MEAN, MEVN - these buzzwords make budding devs blindly use frontend libraries and create SPAs that would be simpler to accomplish with SSR
You’re gonna love my 2023 frameworks video :)
@@t3dotgg oh so that's what that excalidraw sketch is for 👀
You can server side render React. And nowadays you do that most of the time, by default.
@@gamerzero6085 in vanilla react?
@@deadlock107 What do you mean by "vanilla" react?
Great to listen to your thoughts about it! Good content
I started to learn Svelte, they have a good tutorial on their website, but I began to understand why the framework is needed and how to use it properly only after I began to learn React.
Vacancies I see locally demand well-known tech. React, Webpack, MySQL etc. Even jQuery is still around. The only "new" thing that's getting listed on a lot of vacancies is Vue.
100% this. I'm about to introduce a React junior dev to Svelte, and I know he's going to have a huge jump start. Learning React leveled my skills up a ton back in the day. React is hard mode. If you can hang with React, then Vue, Svelte, Solid, and anything that comes next will be much much easier.
react logo is best so that means it's best frontend tool
LMAO no
I started learning it this week. Not new to web development. I just took a long break. I remember when XHTML started replacing HTML 4. Most pages had table layout.
W take Theo
Really useful vid - thank you!
Thank you!
React knowledge is transferrable. You learn React, you'll also learn Solid, Svelte, even Vue.
Lol, this is patently false. Spoken like a true JR
@@FainTMako you make the claim it was false then provide nothing to back it up. sounds like you're the JR.
@@headlights-go-up ok sure? Nothing in react is really similar to svelte in terms of how you implement those systems so other than the fact that they use js.. they aren't really teaching you anything extra. You're still going to have to go through the svelte docs for most things you're wanting to do because react doesn't do it the same?
@@headlights-go-up You got anything to back up your 2 liner? JR?
I tried solidjs and basically wrote react.
as long as there's a demand for it, its never too late or dying anytime soon
When I became a Vue expert, almost all the best practices in Vue applied to React and Angular. Now a days, all 3 frameworks do the same thing, they just emphasis on different aspects of coding. Just learn the different popular code packages and key words.
thanks theo
Also so many codebases are in React. They’ll need people to maintain and develop new features in.
goated chanel
Even after something like Qwik or Svelte supersedes React in the “cutting-edge” space (I honestly feel like Qwik is gonna be the one to do this), there’s still gonna be legacy React codebases for years after this happens. Big companies aren’t moving to “cutting-edge” tech anytime soon.
You read my mind , oh god you’re good
I already knew this but it was motivating
translation: learn leptos bc even if the company requires react, they will let you learn it on the job
It’s never too late to learn anything!🎉🎉
Thanks this make my anxiety gone
Exactly! And and thanks to meta frameworks we will always have the fresh tools
Before React docs beta, we had Dan the Man answering all our questions, so it wasn’t all that bad!
thanks for the reassurance that I really neended.
You're right, learn your lessons, folks. Driving components by rendering cycle and trying to hide state with magic hooks bound with some naming conventions is a bad idea, that is a lesson. And it is time to forget about React, there is a ton frameworks which are doing better job to hide complexity of implementation and which are allowing to structure the code better.
Totally agree! The new functional React docs are so much better than the Class docs were.
react has pros and cons, i learn one and be able to understand so many other derivative framework is nice. however a lot of companies aren't this advanced as they are not usually frontend focused then react wouldn't appear as important since they can't move on
It's so dominant that there will be react work for decades to come. Sure qwik, solid etc are impressive but they aren't going to take over the way react did. Bigger than the tech itself is the community, support and ecosystem around it.
The way I see is that become expert in one SPA framework like React, Angular, and Vue. Then transitioning to others are much easier to learn. At the end all these are tools to solve a need. I don’t think any of these tools are vastly better than other… assuming they all use TS. I just hope browser would one day run TS naively…..
As much as I enjoy Qwik/SolidStart right now to play around in the ecosystem, for prod I'm still React. It'll be a while and some maturity until I feel I'll be confident enough to get where I am with React. I never enjoyed vue/svelte, and kept off that hype-train, and feel it was the right decision. Qwik/Solid with vanilla-extract I am liking though. Still hate tailwind.
You'll come around to tailwind
@@t3dotgg I don't think so. I don't see the use outside of quick product demos.
your thumbnails are too damn funny
the typical w from Theo...
It's still a good time to learn FORTRAN, so, yeah!
If you’re already pretty comfortable coding in JavaScript/Typescript, React doesn’t take that long to get comfortable with, might as well
It's time; we need a hairstyle tutorial
It's never late to learn something. The important thing is not to know something but the path you take to the knowledge.
So is it a good time to learn jquery? (just joking)
@@vvelarm Why not ? 😁
There will be piles of react code to maintain for decades to come. There's still companies running Perl from the 90's. If you're happy with maintaining legacy spaghetti code written in a forgotten tongue, you'll def. make a decent living.
These docs are awfully good!
Dan should be a saint
react uses components paradigm as all other more modern frameworks / libraries. You know one you'll easily learn another one
Angular didn't take off somehow
Angular is a framework. React is a library
I'd be more than happy to use something else if I were getting paid for it. They are nice. But I choose react at my company
Is there even anything else for Web3 in special? I only use React and nobody else seems to do it different. Im very new
Its about time. React current docs are more beta then the beta docs.
Hi Theo, I am learning react with function components. Should I learn class components also?
Not Theo, but I don't think so. The beta React docs that he mentioned strongly recommends functional over class components, and most new React learning materials I've read/seen ever since I started learning (~10 months ago) are using functional components over classes
Is it too late to learn assembly language?
The reality is React is not going anywhere. It has become the standard for Web Apps. Only if the whole industry switches then we'd start worrying about it and with Vercel spearheading Next.js, there's no better time to start diving into React.
Such a good point about other devs wanting* to “hype you up on X framework/tech” 👍🏼
Is too late to learn Fortran?!
❤️❤️❤️
Still waiting for qwik+solid!!
Can we agree Angular Observables inspired react...just a lil?
43 years old learning React.
34 and started learning React
I stopped learning. I realized that for the data intensive crud apps I create Angular does the job just fine because speed and loading time are not of such a big importance. And the speed is more than okay anyway. Each time they mention a framework feature they should mention what type of webapps it targets.
@@paulholsters7932 I jumped onto SvelteKit which is amazing, coming from a python/django background, I find svelte very nice to work with. Never used Angular before.
@@scott_itall8638 It is good. I tried it before. But for data-intensive apps I prefer Angular.
@@paulholsters7932 Yeh cool.
chatGPT + React DOC = Easy $$$
chatGPT will help to explain functions or even comment over your provided code.
I would say... teacher who want's to help :))
Poor Dan Ayybramov 😂
Is it too late to learn php?
There’s people still making a living out of php.
Making lambos, even
Sneaky "React is a framework" take there ar the end, eh?
Been learning React.js for 2 years!! building projects upon projects using available APIs and building my own. I want to move to Next.js at some point this years thanks to some of your videos ! :) excellent work :)! I'm avoiding tutorial videos and just building through my understanding of the documentation, is this ok? Or best practices can be learned through sitting 30 min watching a guy building an app from scratch ? dream is to get a job as a junior one day!
Bro you should be junior after two years.
@@MyPhuckDub I haven't really applied to jobs man. I initially started because I thought it was fun. This year though, I want to move to development and get senior in react. I'm in tech but Im seeing myself coding most of the time. Hopefully soon I can do this.. difficult to find entry level react roles y London, very competitive
Alex Russell left the chat 🙂
you should go on lex friedman
No.
Yes, time for leptos
You’ll still learn programming patterns and better understand a solid framework to base understanding off of.
Is it too late to learn Latin?
I have always view react as an overcomplicated framework and i pick for me and the software we develope Vue or Svelte. Ofc this is opinion based, but they are just so more elegant and easier to use. React just seems like ugly tech
To be honest, the creators of the new frameworks took a lot from Angular, not React. But React is still the most popular.
React is not enjoyable neither is Gatsby. I like the things you can do with Gatsby but just lord I hate using it. I sad you pretty much have to do React to get a job.
IDK what it is but svelte feels like cheating.
Nsme
I hope react will last forever
I dislike all these types of frameworks, there is so much boilerplate crap in the setup. I get it for large projects, there is no way around it, but for smaller ones...
I see some "tutorial folks" spending hours with their tutorials for a simple hello world, stuff you could've written in vanilla js with some css in 10 minutes.
There is a lot of "laziness" to these frameworks, package for this, component for that and panic when there is no package/component. I use alpinejs/vimesh-ui (for components) and tailwind JIT all via CDN's. A single exclamation mark in vs code and I can start, love it.
SEO/marketing must love you!
Almost no projects are small enough to justify vanilla JS these days
Learn php
Actually Its time to learn to deal with chatgpt instead
I am with you on this one 😌
Nah overrated
Thing is Theo, the frontend is still kinda Far-West-y. New frameworks come, new ideas come to frution, mindsets change, paradigms shift. Additionally, no tech rules forever, or at least commands a significant market share. So, the "there will be jobs in React for decades" sounds kinda biased. Remember when Angular was all the rage, when people only said they knew "MEAN" without even knowing what half of the Javascript they wrote does? Where are these stacks now?
Wouldn't new AI kill most of the react dev work ?
Is it too late to learn software development? #chatgpt