It always amuses me when people say a particular language is "dying". Even in this video there's a reference to PHP being from "way back" but thousands of modern sites that people use on a daily basis are still running on PHP. Many of Panasonic's manufacturing processes are built on Perl and still being updated in Perl. One thing I've learned over my 30+ years in tech is that opinions without data are just white noise and can be ignored.
ITS DEAD, its just being used because 90% of companies cant be bother to REWRITE their legacy code. If they had a choice, no company would use trash PHP LOL
yeah, dying is the wrong term, no tech really ever dies... i do think these technologies are falling out of favor for sure. the vast majority of people who prefer using these older technologies are those who are already used to using them or already have established projects that use them. but they certainly arent dead and probably will never truly die.
I'm a freelance web developer for 9+ years now. Over the years I developed my own PHP and Javascript framework, because all of my long term customers had similar issues and problems with common frameworks (like missing features, speed issues, unflexibility). I'm very happy with that decision.
People think that PHP and WordPress and Laravel are dying, hell even JQUERY is still putting out new releases it seems it takes a lot for anything to be dying.... 😂
Great run down. I've been using React at work for a bunch of enterprise projects the last few years, and based on what clients are asking for, I don't see that changing anytime soon. That said, on all my personal projects, Svelte (+SvelteKit) it my go-to, it's so much quicker and (imo) more fun to write.
One thing important to mention is that there is a big confusion between AngularJS and Angular. AngularJS it is very old and I wouldn't really want to use it to any project, but modern Angular is amazing and definitely better then any other framework out there.
@@the_unico Definitely not and depends on use case. For quick prototyping of apps, nope, it has a lot of boilerplate, it has it's advantages with it's stricter nature, there isn't a single framework to rule them all.
@@PatalJunior Take a look at the newest version of Angular, the boilerplate has been reduced dramatically, and they have introduced signals which makes the framework truly reactive. Angular is the only true enterprise worthy solution, and now it can compete for startups too.
@@DouglasWhite-y4s I agree partially. Signals is a step in the right direction. Thought, Signals doesn't handle async or handle race conditions, resulting in the need for yet another third party library like RxJS to do so. I'm an Angular fan, but it still has a long way to go in terms of what I would call "exhaustive reactivity".
I'm a hobbyist (I was in the industry in the late 90's unto the 'Bust', mostly working with ASP and ColdFusion) but I always liked messing around with JS just for the immediacy of the experience. Over the years, I've moved on to other occupations, but in my spare time, I like to build web apps for my own use. A workout tracker, a searchable music library, grocery shopping list/tracker etc. And although I've dabbled with Backbone, Angular, React, Vue, et al, I keep coming back to simple, well organized vanilla javascript, basically using a Publish/Subscribe bus to manage UI state. All the components are on a "need to know basis" and only concern themselves with listening for events that concern them, and update accordingly. Build a store module to contain all your CRUD and XHR logic, and away ya go.
True. Plain JavaScript is much simpler and readable. React does simple things in a convoluted way. I have only a limited knowledge, but this is what I feel.
WordPress using React as the framework for Guttenberg blocks will keep it relevent for many years to come. PHP & React may turn out to be quite a powerful combination.
I am using Svelte. The benefit of Svelte is really "SIMPLE". React is somewhat "COMPLICATED". Also, Svelte gives me a powerful tools and generate a small bundle size.
I would love react to die. Most job opportunities in my country is just react jobs and HRs started to asking not how much experience a Developer has but how much experience in a framework he has. It is crazy.
To me the best part is that if you already know react, you've probably done the hardest part of the journey. Learning these new frameworks is usually simpler till you really need to do crazy stuff
Not at all, React leaves you with tunnel vision and probably if you migrate to another framework such as angular you will find out that you were making junk code all your life. I've come across engineers who didn't even know how to use ngrx or ts correctly.
@@mmadictos5356 But angular is java abstraction and alot of boilerplate with goal for long term support of a project where usually you wanna make something in really solid way where deadlines doesnt really exists compare it to corpo and software house, so I have no idea watcha mean tho, lmao also comparing angular to react or some sort of is the most idiotic comparasion you could have made altho they have alot of similiarity and thats what Juan meant id say. You saying that you have come across those who didn't even know how to use ngrx... like bro... ngrx is such a complex tool comparing to tools like zustand, redux or anything else whats around state managment or reactivity. I havent seen more complex tool like rxjs... for state managment its like learning something totally new also all those tool are only used in angular ecosystem and thats why theyre still alive smh, its all about the angular abstraction and whole convention thats pushing others away of learning it, thats why angular isnt the most friendly tool for frontend development, angular actually due to statistic has the lowest satisfaction of use in developers votes and it drops every year in context of the satisfaction of using it across others tools for frontend or web overall. React is a lib and the opened ecosystem makes it amazing, its such a good tool that doesnt pushes any abstraction, its not opinionated and really close to vanillia js. If you talk about junk code and react you could be right due to angular usage in long term projects, the code is usually really well written due to high usage in corpo ecosystem, react is mostly used in software houses where theres totally different way of work and goals on the table. Each tool has own goal and usage in x situation, but youre kinda acting like ure judging all those from react ecosystem just they couldnt use in first place somebodys abstraction, which is pepega lmao else about the ts "correctly" part... angular is heavily based on ts, where its more strongly typed than other apps most of time, but it really depends especially that most of time you dont really need advanced types with dynamic generic props or anything like that and simple unions etc are enough most of time also generics arent seen that often in React ecosystem especially for components both tools have different way of work even tho both use ts the usage is slightly different. Angular goal is to be tight and heavily developed for long time in really big projects where you need really deep control of everything that's also why rxjs is used for the state and reactivity aspects due to the deep control of connections in pipelines etc. Angular Devs are usually amazing developers with really good knowledge about development and you can learn much more in angular about whole process of development especially as a junior, but it seems like you look at them like from the top of some sort of ego and i highly recommending to drop it down cause angular is like different world and mindset and i can clearly see it right here, right now.
The coolest FE stuff I have done in my career was back in late 2000.. and our Flash SPA:s with AS3 typed language, “easy” state handling, seamlessly merging advanced vector animations, regular content, streaming video, a headless architecture against backend with complementary third party services, broadcast/socket connection between clients etc etc..with 99% browser support. Then came apple with their new hardware that wasn’t strong enough to support that kind of content (and didn’t want to rely on Adobes tech) and a widespread opinion that the web should go back to basics more and be used as originally intended spread at the same time. For a few years we started doing the web just like that to accommodate the weaker mobile devices and cellular bandwidth. Our SPAs became mobile apps instead and the devs and projects got divided into app or web development. But we all know the traditional web is a bit boring so slowly we webfolk started to step by step go towards the cool heavy clients with the shajizz and shajuzz and fast UI response times again.. this time with javascript (that apple approved of) and ended up with heavy JS spas and frameworks once again. Until we thought.. hey these heavy client spas is not how the original web was intended. We need to bring more back to the server and use the web as it once was intended to function.. My guess is that 2025 is the year of the heavy client SPAs again 🙂 I am really likeing our ongoing project though with next 13, server components, type script against a backend/cms that auto-generates interfaces to be used by FE etc etc.. maybe it’s the perfect balance between heavy client spas and not.. But I can’t shake the feeling that we did cooler stuff back in 2007 :)
I lived and breathed the same stuff as you back then (my very first job was a Macromedia Shockwave developer in 1998), and can empathize with all of your points. AS3 was really amazing. It's actually been pretty frustrating for me watching everyone re-invent the wheel over and over, and a lot of times it feels like one step forward, two steps back. It feels like all of these new frameworks are constantly rolling out with tons of hype, but a severe lack of features that only truly weathered and experienced developers understand are important. I don't know how many times I've tried picking up something new just to find out it has a major oversight and requires a number of workarounds to fix, if it's even possible. I can't wait until the TypeScript ecosystem finally has a solid, almost universal framework that's got everything figured out.
@@DougKulak Is it generational? I mean, mullets and staches are making a come back, Ron Jeremy style, right? At what point does some Gen Zer release a YT video about vanilla JS being the best thing since sliced bread, and it takes the world by storm?!?! 🤣
Interesting to see how React is evolving. I'm not much of a web developer but with my limited experience I would find it hard to develop an app without being able to code both the client and the server middleware. I'm currently using custom web components and feathersjs, but my next web app if there is one will probably be React.
Am a solo learner, when it comes to general web dev. I've learned Reactjs almost twice using two different courses, I couldn't get my head around it. But when I took svelte once, it just stick all at once. Am very grateful for Svelte and Sveltekit. Svelte's "magics" are not magic after all. To me Reactjs is full of some tricky magics which I found very difficult to get my head around.
I feel Qwik has the potential to be a game changer. Any thoughts? Angular also seems to be making a comeback with signals but still needs to be more simple and intuitive to get a grasp on imo
I have been working on Angular and React for a while now, and I believe the learning curve of Angular throws a wrench in a desire to continue. I like both, but Angular is more of a challenge
React isn't going anywhere since it's been the largest framework for years. The sheer amount of libraries and projects that depend on it is so massive that it cannot go away. New libraries are good, they bring something fresh but they are only useful when you start new projects, anything else will just be "it's not worth the effort".
@@FS-yq9ef Yes performance optimization with useCallback and useMemo is hell, useReducer adds a lot of code and complexity compared to other frameworks, ...
@@FS-yq9ef Agreed. It's bad when we can't take a step back and think objectively, "Is this truly more efficient?" When the "socially acceptable norm" has become more bloated and complex than more primitive alternatives? It's like asking a 30+ year experienced structural engineer to build a bridge, yet a 5th grader can do so in a fraction of the time (queue the marshmallow challenge). So many bad habits and "norms" have been engrained in developers today that they can't even provide speak to basic JS methods in job interviews.
Glad to know react isn't dying. And of course not, there are tons and tons of framework and libraries depending on it and an ever growing community of developers backing it. Not to mention Facebook, the big tech behind it. It's easy and straight forward approach to programming with components and it's one-way data binding makes it simple and easy to learn. For me simplicity and standards trumps bleeding edge tech..
I'd call react anything but straight forward once you start building real products. The too-low-level abstractions it provides are too flexible for it's own good and it's easy to clutter components with hooks that are completely under the hood in other frameworks (i.e Svelte), and that's before we even talked about page optimization. Regardless, React isn't going anywhere as the amount of projects already build with it is huge and there is a large developer community supporting it.
I wish react were dying. By comparison svelte and sveltekit provide a smoother and simpler developer experience that’s much closer to vanilla web development compared to react’s abstractions and shadow DOM. As a former react developer I picked up svelte in a day and never looked back. Not to mention it’s like 4 times faster and doesn’t ship an entire framework to the client
I actually see Angular rising in a lot of enterprise projects. Not every small landingpage is using Angular so the share is lower - but do you want to work on enterprise or landingpage level?
Wow, your arguments are very well founded it shows that you are a good developer. I am rather developer seen js but when svelte 3 came out and sveltekit, I fell in love with this framework and when Evan you said that he was inspired a lot by svelte currentlymnt, I do not stop developing under svelte, in any case thank you for your explanations
I'm an angular developer since 2019. Should I learn react? I would be no where near my angular skills. Or should I take the latest best framework available. I have a job in Angular and feels like I have learnt almost everything required for a developer in angular. Is it time to grow my tech stack?
Gosh I remember when MVC frameworks like Backbone had become popular; I had become a little burned out from keeping up with them. When React started becoming popular I kind of drug my feet a bit to learn it and Angular. But I think it is important to understand the strengths and weaknesses of popular frameworks/libraries so you can make better choices depending on the type of project.
It begs the question of build vs buy. It would be interesting to see the amount of time developers spend on evaluating and testing FE frameworks versus the amount of time it would take to build components in vanilla JS. Riddle me this ;)
Great explanation! Can you explain how these server components work a little more? I’ve been trying to figure them out, but run into issues when wanting to use a react hook like useState (‘use client’), and an event handler like onSubmit for forms (can’t be client). This seems to complicate things, but I’m probably missing something.
I've been using Svelte (mostly sveltekit) for quite some time now (about 3 years) and I didn't find any problems I couldn't overcome. There's no need to understand "how the magic works", it gives a better understanding but all you really need is to look at the documentation. Also, react has a very large ecosystem of libraries but it mostly consists of wrapper for existing libraries. With svelte you don't need wrappers, you can use the packages as their docs describes because Svelte is so much closer to vanilla javascript.
@@ropoxdev delusional... hence the .JSX extension... either way, I take vanilla JS or any framework that compiles to vanilla JS over any other framework that needs to load client-side completely.
I think if we talk about the customisable and configuration of Svelte, it becomes so powerful, especially with SvelteKit, but the difference is how far you want to go, but of course, React is not going anywhere at least for three years,in case React team did not change or doing something with thier approch.
Svelte struggles with larger scale apps with lots of functionality which React and Angular can better handle. I don't see a new framework with the capability to fully rival those two
From this perspective, I think that's because it isn't easy to manage large codebases, as there can be a lot of duplicated code between components. and that's right, but my friend I think React is the same as Svelte with this!!! maybe, you would be right with the(built-in state management system), but that was 6 months ago you have to read the docs for state management, and React can't even handle the forms in an appropriate way !!!
I think, especially among JavaScript frameworks, that the usage stats are mostly misleading. What I'd really like to see is usage over time for long-term projects - say by combining total commits, total pull requests approved, average commits per year, and average pull requests per year.
I'd like to see the stats include some demographic of the companies at which they work... how many from the Fortune 500 companies vs startups vs non-FAANG. Those stats are more interesting to me personally. Of course the 30 year old developer at a Fortune 100 company is going to hate using Angular when they personally want to work on more "hip" and bleeding edge frameworks like Astro, Svelte, Lit, etc.
"Angular is dying"? It went from 41% in 2018 to 43% in 2022 according to the (awfully distorted) infographic you showed ... that image is terrible it implies the curves are indicitave or perventage movements when they have no consistent correlation at all
if anyone learn react he is a true developer in case if try to implement new feature from scratch, but on other hand , at servlet or any new easy to use framework, the developer have no in depth knowledge in how to implement any new feature from scratch , so core code is better than framework where user do not know anything how to implement new complex feature from scratch.
I'm a complete beginner trying to learn either react or svelte. Can someone experienced tell me what they'd recommend me? I feel like from what I've been reading that svelte has better dx, whereas react has better job opportunity. Please correct me if I am wrong
A couple questions 1) will the React course include this new server side components? 2) a couple months back, I was trying to determine what language I should use for the applications I want to build and came up with the conclusion that if I want an app to change what the user is looking at often (such as having a chat box), I should use react. If I don't have a lot of render changes, I should use angular because it's more strict and robust which makes having a team of developers stick to standards and have cleaner code. Is that actually true? That chart of angular having less people want to go back scares me into learning it and makes me feel I should just use react for everything.
php is not dead. Java is not dead. C# is not dead. Basically, they can never be dead. Well, there are a few extremely rare exceptions (rip Adobe Flash Player)
Of course not. Because big companies want stability instead of finding out that in the middle of migration to new technology that technology became outdated. I worked for company that maintains software for government institution and they will never ever want to migrate to any new technology as long as old one works and fulfills requirements not because of complexity of migration but for the reason that you will never ever will be up to date with these days technologies anyway.
Every 17.6 weeks or so another new JavaScript framework comes out, and within 3.9 days after the release, another 6.4 UA-cam developers have a new video about how this new framework is - or is not - going to kick React to the curb, like a JS Framework game of "king of the mountain."
Also worth mentioning every new framework or library promises to be easier to use, more performant and solve problems better than any competitor. They never do in real enterprise projects.
I've been told react react react but I've been learning svelte and it's been a really enjoyable experience. I'll learn react if i need to got a job but for now I'm gonna stick with svelte. I've heard good things about solidjs also but i don't know much about it
This is what is meant when people say React is dying.DEVS ARE CHOOSING BETTER OPTIONS THAT ARE EASIER TO WORK WITH: Not that react won't be around in a year, of course it will. Devs in coming years will have to maintain these awful codebases build on React with Next, Redux, MUI etc etc etc all that randomness that React labelled "flexibility"", that is really just unmaintainable 3rd party add-ons from hell.
@@Daijyobanai 5 years from now: "Svelte sucks; devs are choosing better options that are easier to work with. Not that Svelte won't be around in ay ear, of course it will. Devs in coming years will have to maintain these awful codebases build on Svelte. All that randomness that Svelte named "magic", that is really just unmaintainable spaghetti code"
@@spell105 yes time will make every web technology obsolete eventually, but at least some of react’s competitors are built on web standards, and not a series of hacks because react was not planned well to begin with.
When people say react is dying they are thinking in terms of SPA. plain react with vite would do most of the beginner works but when it comes to MPA with SSR Nextjs is the beast or there and Iam not even considering app/ directory which has server component by default even as simple as getStaticProps pre-renders on the page can solve much of the complex problems out there anyways react is not gonna die
React is the PHP of Frontend Javascript Libraries. Its not necessarily the best but it was the best option at the time it was needed most, so it powers the majority of dynamic frontends, and will for a long time to come.
Рік тому+3
You're mixing up things, comparing a library with a language.
I don't think vue gets enough credit. It has composition api that very similar to svelte and with vapor right around corner it can be compiled without vdom very similar to svelte and solid. It also has a large community and ecosystem. Nuxt 3 for example is awesome for full stack. With Nuxt 3 I have switched from react to vue and haven't looked back. The mental model is so much easier, and with composition api I get a svelte like coding experience with a larger ecosystem and community.
I dont really get why it too. Vue can do pretty much what react can do, and in a cleaner and easier way, at least for me. I'm trying to learn react now, and there's so much things to do that you can do easily in vue.
@@danbizirean4196 reactivity in vue is very similar to solid, but the updates are done via vdom (until vapor comes out, then it will use micro updates similar to solid and skip vdom). It has less magic than svelte when using composition api which is svelte like. If you use options api it uses zero magic and you can even embed directly in browser unlike react and svelte. Typescript support is much better in latest vue, latest vue itself is written in typescript and all core libraries fully support typescript and bundle/export all type declarations. I can get a lot of the benefits of svelte (composition api), solid (reactivity and soon vapor), react, all wrapped in a framework that is the third most popular js framework which has larger ecosystem than something like solid or svelte.
@@danbizirean4196 1. It's a false statement 2. What exactly do you miss in Vue's ecosystem? 3. Vue 3 has a good TS support (and improving in every version) 4. True, but it won't stay in your way. You can even use JSX in it. Also, not a problem for me. 5. Less jobs than React doesn't mean no jobs at all. I'm working as a full-time Vue developer and it has been amazing.
Your comment about "I don't need to know how hooks work" (with React) by using Svelte is quite subjective. With Svelte, you need to know the template syntax which, in my opinion, adds a layer of complexity that is disconnected from both HTML and JavaScript. React hooks are JavaScript (or TypeScript), and do not add to the language; you just need to know how they are used. With Svelte, it's en entirely new thing to learn ON TOP of JavaScript/TypeScript and HTML.
Рік тому+2
The only way React is worth is learning its practical peculiarities; with theory is quite difficult to grasp its potential. So learning it thru courses like yours is the only way.
yeah man be rational and dont just be hype or jump into another framework/tools too quickly .., js-lings arguing each new JS framework came out and in other side, another lang want to JS itself died or getting replaced by their own lang as fast as it is possible
Absolutely! Find me a CTO willing to put their job and equity on the line to approve a wholesale change in tech stack. Won't happen, no matter how jazzed up his/her engineering team is about the next bleeding edge tech stack.
Angular is a framework to creat a complete frontend. Unlike ReactJs. So Angulars scales out of the box - big projects. ReactJs has no structure, no architecture. It's just a library. So you're wasting time installing all these libraries in ReactJd just to make it usable. I can't see why would Angular die!
I believe that a new framework or library can only replace older ones if it significantly improves the user experience, rather than just the developer experience. For instance, React became more popular than older languages and frameworks like PHP and jQuery due to introduction of ES6(modules) , virtual DOM, and client-side routing. When a business decides to migrate to a new technology, it needs to evaluate the benefits of doing so. Therefore, I think that React, Angular, and Vue will continue to be popular unless a new framework is introduced that significantly enhances the user experience.
React isn't more popular than PHP though. You still have a ton of websites and services running on PHP. What React did is to make it easier to scale a frontend part of an app. Which PHP have issues to do. But PHP is good at scaling backends, so people use it for backends while React handle front.
The original value propositions for Svelte and Solid include prominently benefits for the end user. Namely performance gains and reduced transference sizes.
I primarily use htmx and Django.I have built saas applications with it and still able to have the single page application benefits without JavaScript fatigue. 1.Htmx is super fast,compared to frontend frameworks. 2.backend agnostic choose express, Django, Laravel whatever you like. 3.locality of behavior. 4.KISS, keep it simple stupid.
Honestly that explains how much people actually care about writing a perfect code. Angular is prepared for anything, these graphs are affected by juniors which actually doesn't really matter. Clients want strong and devoted developers
not yet but companies are using what react did with their framework and use it in the languages they back up. Apple using SwiftUI to implement logic behind the view and used to change page, I hope to see server side framework that can implement some react and eventually replace it with some html like framework to display things on server into pages. Microsoft forcing most users even ones limited to mac os to use razor pages on visual studio but its possible to just use the server side.
The short answer is "no, react is not dying, but it should". Effectively it's a legacy tool. No reasonable SFC styling solutions, platform events replaced by synthetic events like it was jQuery. No new projects should be started on React in 2023.
You may have misread the chart. At the moment when you said "Angular is dying" is was actually showing increased awareness. It was just ranked lower because there were a bunch of newer frameworks in the ranked list. Angular appears to be experiencing a renaissance.
Sure it's not the new hot thing but every year a big portion of developers that work with C++ retire that needs replacing with new talent. It's going nowhere and will probably get a new boost in the future when people jump to the next hot thing which happens to involve c++.
Yes and that’s okay, so many things are easier in frameworks like svelte or even vue, we should always use the best tool for the job, not the one most popular. Also as a developer you should be able to use any framework to do the job. If you only know how to do thing X in angular, you should invest time in learning other tools.
I think the React team is doing a few things in the last couple years that do not represent evolution or are not good at all (like all the logic behind hooks and their names, and their "rules"), specially because many things there are not intuitive, which is the opposite you expect as a developer. Other example is that React is always introducing new concepts and throwing everything you learned in the trash - for example the changes in the react-dom api and everything about class components. Solid seems to be a great deal in comparison to React and other great simpler frameworks like Vue and Svelte, and it leverages the best thing in React in my opinion: JSX - and still has a nice simplicity as Svelte does. Looking forward to experiment that in a future project. For now, long live to React.
React was never meant to be intuitive, the first mistake beginners always do is try to mutate state directly because that's the intuitive thing to do and its wrong
Okay, I love you man and I'll watch this video later. But I don't know if this is a click-bait or not (since it's a question). But the answer is no. React is not going anywhere, anytime soon. It's probably one of the most frame (or rather libraries out there) followed my Angualr and Vue. Even the Vuestorefront which is a Nuxt framework for vue, has adapted the usage for React as well. Tesco Tech, one of the largest retail markets in the world uses React For their ENTIRE platform ICF and most streaming industries Zeiss is currently moving it's B2B stack from Angular to React (I interviewed with them this year) Just lookup on Indeed and Linkedin, React is relevant and is not going anywhere instead of trying to learn a thousand frameworks, people should get themselves familiar with CI/CD, Docker, Cloud basics, Devops in general because that shit is spreading like wildfire. I'm serious. Good God, DevOps should be it's own profession, why the fuck are Frontended engineers required to master it! Also in terms of PHP, a lot of people used to say that it's dead.... but PHP is still widely used The same goes for Mainframes, people keep saying they'll die, but there doesn't exist a single computing device that can compute mainframe speed or security. No they're not dead but the older generation is retiring and it's not taught in Universities which is bad. Even people who says cloud is replacing servers...... Don't realize that cloud is basically a network of servers? You're just not owning your own servers but rather renting out servers... like owning a house vs renting an apartment. No React is not going anywhere, nor will it.
What I don't like about the graph (0:52 - 4:30) is that it does a poor job of presenting the trends. Whenever a new framework is introduced, all other frameworks get pushed down, making the existing ones appear to be losing popularity. For example, Svelte in 2020 was showing 89% and "dropped" to 90% in 2021 to make way for Solid. I understand that each annual column just stacks the items top to bottom, most to least popular. I just think it could have been presented in a less confusing way.
Software languages or frameworks increase abstraction as they mature and add features and new ones are released with less abstraction and less overhead.
It always amuses me when people say a particular language is "dying". Even in this video there's a reference to PHP being from "way back" but thousands of modern sites that people use on a daily basis are still running on PHP. Many of Panasonic's manufacturing processes are built on Perl and still being updated in Perl. One thing I've learned over my 30+ years in tech is that opinions without data are just white noise and can be ignored.
ITS DEAD, its just being used because 90% of companies cant be bother to REWRITE their legacy code. If they had a choice, no company would use trash PHP LOL
yeah, dying is the wrong term, no tech really ever dies... i do think these technologies are falling out of favor for sure. the vast majority of people who prefer using these older technologies are those who are already used to using them or already have established projects that use them. but they certainly arent dead and probably will never truly die.
PHP? 🤣🤣🤣🤣🤣
@@frederiklist4265
🤣🤣🤣🤣🤣🤣
True
Yea this dude ain’t a programmer Lmaoo
I'm a freelance web developer for 9+ years now. Over the years I developed my own PHP and Javascript framework, because all of my long term customers had similar issues and problems with common frameworks (like missing features, speed issues, unflexibility). I'm very happy with that decision.
Terrible. I mean great for you, awful for your customers.
I'm on the way to freelance, but it's hard.
I use php, nodejs, vue/react
@@w3hacker
Terrible. I mean great for you, awful for your customers.
People think that PHP and WordPress and Laravel are dying, hell even JQUERY is still putting out new releases it seems it takes a lot for anything to be dying.... 😂
Laravel has been paid my bills for 6 years straight
PHP: Laravel and Wordpress represents more than 65% of my revenue until today.
The other 35% are divided between python and react applications.
Great run down.
I've been using React at work for a bunch of enterprise projects the last few years, and based on what clients are asking for, I don't see that changing anytime soon.
That said, on all my personal projects, Svelte (+SvelteKit) it my go-to, it's so much quicker and (imo) more fun to write.
Hii can you guide how to draw polygon on map in react and get coordinate of vertices
@@OpenMinded2509
I would suggest you to use Gojs
One thing important to mention is that there is a big confusion between AngularJS and Angular.
AngularJS it is very old and I wouldn't really want to use it to any project, but modern Angular is amazing and definitely better then any other framework out there.
I don't think any 2020 + video in youtube thinks of AngularJS when they mention Angular. This is ancient history.
Yeah bro. Angular is one of the best front end frame work right now.
@@the_unico Definitely not and depends on use case. For quick prototyping of apps, nope, it has a lot of boilerplate, it has it's advantages with it's stricter nature, there isn't a single framework to rule them all.
@@PatalJunior Take a look at the newest version of Angular, the boilerplate has been reduced dramatically, and they have introduced signals which makes the framework truly reactive. Angular is the only true enterprise worthy solution, and now it can compete for startups too.
@@DouglasWhite-y4s I agree partially. Signals is a step in the right direction. Thought, Signals doesn't handle async or handle race conditions, resulting in the need for yet another third party library like RxJS to do so. I'm an Angular fan, but it still has a long way to go in terms of what I would call "exhaustive reactivity".
I'm a hobbyist (I was in the industry in the late 90's unto the 'Bust', mostly working with ASP and ColdFusion) but I always liked messing around with JS just for the immediacy of the experience.
Over the years, I've moved on to other occupations, but in my spare time, I like to build web apps for my own use. A workout tracker, a searchable music library, grocery shopping list/tracker etc.
And although I've dabbled with Backbone, Angular, React, Vue, et al, I keep coming back to simple, well organized vanilla javascript, basically using a Publish/Subscribe bus to manage UI state.
All the components are on a "need to know basis" and only concern themselves with listening for events that concern them, and update accordingly.
Build a store module to contain all your CRUD and XHR logic, and away ya go.
True. Plain JavaScript is much simpler and readable. React does simple things in a convoluted way. I have only a limited knowledge, but this is what I feel.
WordPress using React as the framework for Guttenberg blocks will keep it relevent for many years to come. PHP & React may turn out to be quite a powerful combination.
Is it good ? Are you using reactpress ? I hesitate to use wordpress in addition to react...
What a perfect combination of shit :D
powerful combination. i think is (C,C++) + html,css,javascript,php. Then You can go forward.
Don't forget to add Next JS, one of the most popular frameworks that many well-known companies are using.
@@luzaw4957 Next is React
I am using Svelte. The benefit of Svelte is really "SIMPLE". React is somewhat "COMPLICATED". Also, Svelte gives me a powerful tools and generate a small bundle size.
I would love to see more content on Svelte. Rich Harris' talks inspire me and it's definitely what I'm going to learn next.
I would love react to die. Most job opportunities in my country is just react jobs and HRs started to asking not how much experience a Developer has but how much experience in a framework he has. It is crazy.
To me the best part is that if you already know react, you've probably done the hardest part of the journey. Learning these new frameworks is usually simpler till you really need to do crazy stuff
Not at all, React leaves you with tunnel vision and probably if you migrate to another framework such as angular you will find out that you were making junk code all your life.
I've come across engineers who didn't even know how to use ngrx or ts correctly.
@@mmadictos5356 But angular is java abstraction and alot of boilerplate with goal for long term support of a project where usually you wanna make something in really solid way where deadlines doesnt really exists compare it to corpo and software house, so I have no idea watcha mean tho, lmao also comparing angular to react or some sort of is the most idiotic comparasion you could have made altho they have alot of similiarity and thats what Juan meant id say. You saying that you have come across those who didn't even know how to use ngrx... like bro... ngrx is such a complex tool comparing to tools like zustand, redux or anything else whats around state managment or reactivity. I havent seen more complex tool like rxjs... for state managment its like learning something totally new also all those tool are only used in angular ecosystem and thats why theyre still alive smh, its all about the angular abstraction and whole convention thats pushing others away of learning it, thats why angular isnt the most friendly tool for frontend development, angular actually due to statistic has the lowest satisfaction of use in developers votes and it drops every year in context of the satisfaction of using it across others tools for frontend or web overall. React is a lib and the opened ecosystem makes it amazing, its such a good tool that doesnt pushes any abstraction, its not opinionated and really close to vanillia js. If you talk about junk code and react you could be right due to angular usage in long term projects, the code is usually really well written due to high usage in corpo ecosystem, react is mostly used in software houses where theres totally different way of work and goals on the table. Each tool has own goal and usage in x situation, but youre kinda acting like ure judging all those from react ecosystem just they couldnt use in first place somebodys abstraction, which is pepega lmao else about the ts "correctly" part... angular is heavily based on ts, where its more strongly typed than other apps most of time, but it really depends especially that most of time you dont really need advanced types with dynamic generic props or anything like that and simple unions etc are enough most of time also generics arent seen that often in React ecosystem especially for components both tools have different way of work even tho both use ts the usage is slightly different. Angular goal is to be tight and heavily developed for long time in really big projects where you need really deep control of everything that's also why rxjs is used for the state and reactivity aspects due to the deep control of connections in pipelines etc. Angular Devs are usually amazing developers with really good knowledge about development and you can learn much more in angular about whole process of development especially as a junior, but it seems like you look at them like from the top of some sort of ego and i highly recommending to drop it down cause angular is like different world and mindset and i can clearly see it right here, right now.
I would agree with you but Svelte has some pretty crazy stuff at the beginning of the course.
@@JEsterCW tldr you’re just mad that somebody didn’t prefer using reactjs over actual “framework” whatever
for me*
The coolest FE stuff I have done in my career was back in late 2000.. and our Flash SPA:s with AS3 typed language, “easy” state handling, seamlessly merging advanced vector animations, regular content, streaming video, a headless architecture against backend with complementary third party services, broadcast/socket connection between clients etc etc..with 99% browser support.
Then came apple with their new hardware that wasn’t strong enough to support that kind of content (and didn’t want to rely on Adobes tech) and a widespread opinion that the web should go back to basics more and be used as originally intended spread at the same time.
For a few years we started doing the web just like that to accommodate the weaker mobile devices and cellular bandwidth. Our SPAs became mobile apps instead and the devs and projects got divided into app or web development.
But we all know the traditional web is a bit boring so slowly we webfolk started to step by step go towards the cool heavy clients with the shajizz and shajuzz and fast UI response times again.. this time with javascript (that apple approved of) and ended up with heavy JS spas and frameworks once again.
Until we thought.. hey these heavy client spas is not how the original web was intended. We need to bring more back to the server and use the web as it once was intended to function..
My guess is that 2025 is the year of the heavy client SPAs again 🙂
I am really likeing our ongoing project though with next 13, server components, type script against a backend/cms that auto-generates interfaces to be used by FE etc etc.. maybe it’s the perfect balance between heavy client spas and not..
But I can’t shake the feeling that we did cooler stuff back in 2007 :)
I lived and breathed the same stuff as you back then (my very first job was a Macromedia Shockwave developer in 1998), and can empathize with all of your points. AS3 was really amazing. It's actually been pretty frustrating for me watching everyone re-invent the wheel over and over, and a lot of times it feels like one step forward, two steps back. It feels like all of these new frameworks are constantly rolling out with tons of hype, but a severe lack of features that only truly weathered and experienced developers understand are important. I don't know how many times I've tried picking up something new just to find out it has a major oversight and requires a number of workarounds to fix, if it's even possible. I can't wait until the TypeScript ecosystem finally has a solid, almost universal framework that's got everything figured out.
I still think that there is no competition with as3 till this day these all things feels hackish. And yes steve is in hell
@@DougKulak Is it generational? I mean, mullets and staches are making a come back, Ron Jeremy style, right? At what point does some Gen Zer release a YT video about vanilla JS being the best thing since sliced bread, and it takes the world by storm?!?! 🤣
Interesting to see how React is evolving. I'm not much of a web developer but with my limited experience I would find it hard to develop an app without being able to code both the client and the server middleware. I'm currently using custom web components and feathersjs, but my next web app if there is one will probably be React.
Proba Svele, esta lejos en facilidad al lado de React!
Am a solo learner, when it comes to general web dev. I've learned Reactjs almost twice using two different courses, I couldn't get my head around it. But when I took svelte once, it just stick all at once.
Am very grateful for Svelte and Sveltekit. Svelte's "magics" are not magic after all.
To me Reactjs is full of some tricky magics which I found very difficult to get my head around.
I feel Qwik has the potential to be a game changer. Any thoughts?
Angular also seems to be making a comeback with signals but still needs to be more simple and intuitive to get a grasp on imo
Svelte really is a joy to work with compared with react, and integration with sveltekit is first class. You should cover it more on your channel
I have been working on Angular and React for a while now, and I believe the learning curve of Angular throws a wrench in a desire to continue. I like both, but Angular is more of a challenge
Your explanation is great, and it's wonderful to know that React is still going strong.
React isn't going anywhere since it's been the largest framework for years. The sheer amount of libraries and projects that depend on it is so massive that it cannot go away. New libraries are good, they bring something fresh but they are only useful when you start new projects, anything else will just be "it's not worth the effort".
It's sad because react sucks. Terrible architecture that I'm forced to work with. The library was built by clowns.
@@FS-yq9ef Yes performance optimization with useCallback and useMemo is hell, useReducer adds a lot of code and complexity compared to other frameworks, ...
@@FS-yq9ef Agreed. It's bad when we can't take a step back and think objectively, "Is this truly more efficient?" When the "socially acceptable norm" has become more bloated and complex than more primitive alternatives? It's like asking a 30+ year experienced structural engineer to build a bridge, yet a 5th grader can do so in a fraction of the time (queue the marshmallow challenge). So many bad habits and "norms" have been engrained in developers today that they can't even provide speak to basic JS methods in job interviews.
Glad to know react isn't dying. And of course not, there are tons and tons of framework and libraries depending on it and an ever growing community of developers backing it. Not to mention Facebook, the big tech behind it. It's easy and straight forward approach to programming with components and it's one-way data binding makes it simple and easy to learn. For me simplicity and standards trumps bleeding edge tech..
I'd call react anything but straight forward once you start building real products. The too-low-level abstractions it provides are too flexible for it's own good and it's easy to clutter components with hooks that are completely under the hood in other frameworks (i.e Svelte), and that's before we even talked about page optimization.
Regardless, React isn't going anywhere as the amount of projects already build with it is huge and there is a large developer community supporting it.
I wish react were dying. By comparison svelte and sveltekit provide a smoother and simpler developer experience that’s much closer to vanilla web development compared to react’s abstractions and shadow DOM. As a former react developer I picked up svelte in a day and never looked back. Not to mention it’s like 4 times faster and doesn’t ship an entire framework to the client
Now yall know how it feels when people say php is dying
I just started learning this. I would have been pissed
@@dima6488 Real projects? Please go on. I’m new to things and never worked in a company before. All I am doing is studying languages now
Angular is evolving too not just React
I actually see Angular rising in a lot of enterprise projects. Not every small landingpage is using Angular so the share is lower - but do you want to work on enterprise or landingpage level?
Yep, I believe to you) My last project on react was a helthCare project for all doctors in my country, it seems really like landingpage 🤣
I've never seen job openings for Svelte. Nobody talks about Svelte where I work either. We do mostly React, Angular and a few Vue projects.
Great talk! From my years of experience I've come to realise that magic can only take you so far. I love React's verbosity
Angular is dying - that made me laught so much xD
Wow, your arguments are very well founded it shows that you are a good developer. I am rather developer seen js but when svelte 3 came out and sveltekit, I fell in love with this framework and when Evan you said that he was inspired a lot by svelte currentlymnt, I do not stop developing under svelte, in any case thank you for your explanations
I'm an angular developer since 2019. Should I learn react? I would be no where near my angular skills. Or should I take the latest best framework available. I have a job in Angular and feels like I have learnt almost everything required for a developer in angular. Is it time to grow my tech stack?
I don't see why not? Don't give up angular though.
Gosh I remember when MVC frameworks like Backbone had become popular; I had become a little burned out from keeping up with them. When React started becoming popular I kind of drug my feet a bit to learn it and Angular. But I think it is important to understand the strengths and weaknesses of popular frameworks/libraries so you can make better choices depending on the type of project.
Many of the wonders of newer frameworks are done with very simple projects. As soon as you get knee deep the story changes
It begs the question of build vs buy. It would be interesting to see the amount of time developers spend on evaluating and testing FE frameworks versus the amount of time it would take to build components in vanilla JS. Riddle me this ;)
Great explanation! Can you explain how these server components work a little more? I’ve been trying to figure them out, but run into issues when wanting to use a react hook like useState (‘use client’), and an event handler like onSubmit for forms (can’t be client). This seems to complicate things, but I’m probably missing something.
If angular’s history can inform this question, it shows that by the time a framework achieves this level of dominance, “the end” Is a multiyear thing
I've been using Svelte (mostly sveltekit) for quite some time now (about 3 years) and I didn't find any problems I couldn't overcome. There's no need to understand "how the magic works", it gives a better understanding but all you really need is to look at the documentation. Also, react has a very large ecosystem of libraries but it mostly consists of wrapper for existing libraries. With svelte you don't need wrappers, you can use the packages as their docs describes because Svelte is so much closer to vanilla javascript.
svelte is cheating, it just compiles to JS. React is true JS
@@ropoxdev delusional... hence the .JSX extension... either way, I take vanilla JS or any framework that compiles to vanilla JS over any other framework that needs to load client-side completely.
ok, so which one is future ? which will be best in use for new projects ? easy and fast
React is like Java: inconvenient but widespread. Too much legacy to replace
I think if we talk about the customisable and configuration of Svelte, it becomes so powerful, especially with SvelteKit, but the difference is how far you want to go, but of course, React is not going anywhere at least for three years,in case React team did not change or doing something with thier approch.
People will be using React in 30 years time from now. People have been saying for 2 decades that PHP is dying and it’s still going strong today
we're not talking about the end of React "dying" we're talking about not being number one.
Svelte struggles with larger scale apps with lots of functionality which React and Angular can better handle. I don't see a new framework with the capability to fully rival those two
From this perspective, I think that's because it isn't easy to manage large codebases, as there can be a lot of duplicated code between components. and that's right, but my friend I think React is the same as Svelte with this!!!
maybe, you would be right with the(built-in state management system), but that was 6 months ago you have to read the docs for state management, and React can't even handle the forms in an appropriate way !!!
I think, especially among JavaScript frameworks, that the usage stats are mostly misleading. What I'd really like to see is usage over time for long-term projects - say by combining total commits, total pull requests approved, average commits per year, and average pull requests per year.
I'd like to see the stats include some demographic of the companies at which they work... how many from the Fortune 500 companies vs startups vs non-FAANG. Those stats are more interesting to me personally. Of course the 30 year old developer at a Fortune 100 company is going to hate using Angular when they personally want to work on more "hip" and bleeding edge frameworks like Astro, Svelte, Lit, etc.
Even with server components, it's 10x more code and complexity than for example SvelteKit or Nuxt way of doing it.
"Angular is dying"? It went from 41% in 2018 to 43% in 2022 according to the (awfully distorted) infographic you showed ... that image is terrible it implies the curves are indicitave or perventage movements when they have no consistent correlation at all
if anyone learn react he is a true developer in case if try to implement new feature from scratch, but on other hand , at servlet or any new easy to use framework, the developer have no in depth knowledge in how to implement any new feature from scratch , so core code is better than framework where user do not know anything how to implement new complex feature from scratch.
I'm a complete beginner trying to learn either react or svelte. Can someone experienced tell me what they'd recommend me? I feel like from what I've been reading that svelte has better dx, whereas react has better job opportunity. Please correct me if I am wrong
Angular is dying :)) Retention 2018-2022: 41%-43% is growing. Ask big clients why they choose it over React.
A couple questions
1) will the React course include this new server side components?
2) a couple months back, I was trying to determine what language I should use for the applications I want to build and came up with the conclusion that if I want an app to change what the user is looking at often (such as having a chat box), I should use react. If I don't have a lot of render changes, I should use angular because it's more strict and robust which makes having a team of developers stick to standards and have cleaner code. Is that actually true? That chart of angular having less people want to go back scares me into learning it and makes me feel I should just use react for everything.
Usa Svelte
Vue. You won't want to look back.
php is not dead. Java is not dead. C# is not dead.
Basically, they can never be dead. Well, there are a few extremely rare exceptions (rip Adobe Flash Player)
Of course not. Because big companies want stability instead of finding out that in the middle of migration to new technology that technology became outdated. I worked for company that maintains software for government institution and they will never ever want to migrate to any new technology as long as old one works and fulfills requirements not because of complexity of migration but for the reason that you will never ever will be up to date with these days technologies anyway.
Can't believe I spent months learning AS3 only for adobe to announce the end of life for flash... ActionScript was my first language.
Every 17.6 weeks or so another new JavaScript framework comes out, and within 3.9 days after the release, another 6.4 UA-cam developers have a new video about how this new framework is - or is not - going to kick React to the curb, like a JS Framework game of "king of the mountain."
Also worth mentioning every new framework or library promises to be easier to use, more performant and solve problems better than any competitor. They never do in real enterprise projects.
@@igorpupkinable Exactly. I can say for certain though: Pascal is dead as a language. C & C++ are still kicking, though.
Frontend has turned into a hilarious experimentation.
I've been told react react react but I've been learning svelte and it's been a really enjoyable experience. I'll learn react if i need to got a job but for now I'm gonna stick with svelte.
I've heard good things about solidjs also but i don't know much about it
This is what is meant when people say React is dying.DEVS ARE CHOOSING BETTER OPTIONS THAT ARE EASIER TO WORK WITH: Not that react won't be around in a year, of course it will. Devs in coming years will have to maintain these awful codebases build on React with Next, Redux, MUI etc etc etc all that randomness that React labelled "flexibility"", that is really just unmaintainable 3rd party add-ons from hell.
@@Daijyobanai 5 years from now: "Svelte sucks; devs are choosing better options that are easier to work with. Not that Svelte won't be around in ay ear, of course it will. Devs in coming years will have to maintain these awful codebases build on Svelte. All that randomness that Svelte named "magic", that is really just unmaintainable spaghetti code"
@@spell105 yes time will make every web technology obsolete eventually, but at least some of react’s competitors are built on web standards, and not a series of hacks because react was not planned well to begin with.
is Angular really dying ? More and more enterprise is using it
When people say react is dying they are thinking in terms of SPA. plain react with vite would do most of the beginner works but when it comes to MPA with SSR Nextjs is the beast or there and Iam not even considering app/ directory which has server component by default even as simple as getStaticProps pre-renders on the page can solve much of the complex problems out there
anyways react is not gonna die
React is the PHP of Frontend Javascript Libraries. Its not necessarily the best but it was the best option at the time it was needed most, so it powers the majority of dynamic frontends, and will for a long time to come.
You're mixing up things, comparing a library with a language.
Would love to see more Svelte content!
Thank you for my career, React 😘
Future: Script Language (nodejs / python / java) + microservices + web components (Lit / SolidJS / etc) + cloud
I don't think vue gets enough credit. It has composition api that very similar to svelte and with vapor right around corner it can be compiled without vdom very similar to svelte and solid. It also has a large community and ecosystem. Nuxt 3 for example is awesome for full stack.
With Nuxt 3 I have switched from react to vue and haven't looked back. The mental model is so much easier, and with composition api I get a svelte like coding experience with a larger ecosystem and community.
I dont really get why it too. Vue can do pretty much what react can do, and in a cleaner and easier way, at least for me. I'm trying to learn react now, and there's so much things to do that you can do easily in vue.
Well actually Vue has poor reactivity system.
Ecosystem is huge problem.
Not nice typescript support.
Lot of magic.
Less jobs.
@@danbizirean4196 reactivity in vue is very similar to solid, but the updates are done via vdom (until vapor comes out, then it will use micro updates similar to solid and skip vdom).
It has less magic than svelte when using composition api which is svelte like. If you use options api it uses zero magic and you can even embed directly in browser unlike react and svelte.
Typescript support is much better in latest vue, latest vue itself is written in typescript and all core libraries fully support typescript and bundle/export all type declarations.
I can get a lot of the benefits of svelte (composition api), solid (reactivity and soon vapor), react, all wrapped in a framework that is the third most popular js framework which has larger ecosystem than something like solid or svelte.
@@danbizirean4196
1. It's a false statement
2. What exactly do you miss in Vue's ecosystem?
3. Vue 3 has a good TS support (and improving in every version)
4. True, but it won't stay in your way. You can even use JSX in it. Also, not a problem for me.
5. Less jobs than React doesn't mean no jobs at all. I'm working as a full-time Vue developer and it has been amazing.
I’ve learnt a new thing today.
I should start learning react that’s y I’m learning core concepts of JS fastly
Your comment about "I don't need to know how hooks work" (with React) by using Svelte is quite subjective. With Svelte, you need to know the template syntax which, in my opinion, adds a layer of complexity that is disconnected from both HTML and JavaScript. React hooks are JavaScript (or TypeScript), and do not add to the language; you just need to know how they are used. With Svelte, it's en entirely new thing to learn ON TOP of JavaScript/TypeScript and HTML.
The only way React is worth is learning its practical peculiarities; with theory is quite difficult to grasp its potential.
So learning it thru courses like yours is the only way.
What framework would u start with now ?
I'd count that as a point against React tbh
Another reason learning React is useful: Some of the newer frameworks bear a strong resemblance to React in order to minimize the learning curve.
Basically React and other frameworks are just tools. As long as the tools are still able to pay people's bills, then the word "dead" is just a myth.
yeah man be rational and dont just be hype or jump into another framework/tools too quickly .., js-lings arguing each new JS framework came out and in other side, another lang want to JS itself died or getting replaced by their own lang as fast as it is possible
Absolutely! Find me a CTO willing to put their job and equity on the line to approve a wholesale change in tech stack. Won't happen, no matter how jazzed up his/her engineering team is about the next bleeding edge tech stack.
Angular is a framework to creat a complete frontend. Unlike ReactJs.
So Angulars scales out of the box - big projects.
ReactJs has no structure, no architecture. It's just a library.
So you're wasting time installing all these libraries in ReactJd just to make it usable.
I can't see why would Angular die!
Very good content. You set the record straight for challenges and opportunities faced by react. Thank you
Kyle you are wrong, AI would take all React jobs
I believe that a new framework or library can only replace older ones if it significantly improves the user experience, rather than just the developer experience. For instance, React became more popular than older languages and frameworks like PHP and jQuery due to introduction of ES6(modules) , virtual DOM, and client-side routing. When a business decides to migrate to a new technology, it needs to evaluate the benefits of doing so. Therefore, I think that React, Angular, and Vue will continue to be popular unless a new framework is introduced that significantly enhances the user experience.
Totally agree. If you migrate just because new technology is a trend - you will never catch up.
React isn't more popular than PHP though. You still have a ton of websites and services running on PHP.
What React did is to make it easier to scale a frontend part of an app. Which PHP have issues to do. But PHP is good at scaling backends, so people use it for backends while React handle front.
@@arakwar they meant React vs SSR PHP. What you said supports their point of view.
The original value propositions for Svelte and Solid include prominently benefits for the end user. Namely performance gains and reduced transference sizes.
@@arakwar
PHP lags many things as a server side technology... Hence it cannot be compared with other popular server side technologies...
I primarily use htmx and Django.I have built saas applications with it and still able to have the single page application benefits without JavaScript fatigue.
1.Htmx is super fast,compared to frontend frameworks.
2.backend agnostic choose express, Django, Laravel whatever you like.
3.locality of behavior.
4.KISS, keep it simple stupid.
I think with Angular a lot of people get into it but don't stay in it since it is much more difficult to learn for beginners
It's not difficult to learn, but difficult to master. 🙂
Honestly that explains how much people actually care about writing a perfect code. Angular is prepared for anything, these graphs are affected by juniors which actually doesn't really matter. Clients want strong and devoted developers
Beauty of react is that it is not framework. you can use it however you like. Frameworks force you to do things the same way all the time. ;)
Beauty and react should not be used in a sentence together.
@@Eldalion99999 why?
It’s a framework lol
@@scott_itall8638 its not. A framework forces a pattern but in React we can apply our own patterns
I have to use Angular for work
can not believe that I became a front-end dev just by falling in love with u ..... I mean with ur explanaation along 6 months ❤
not yet but companies are using what react did with their framework and use it in the languages they back up. Apple using SwiftUI to implement logic behind the view and used to change page, I hope to see server side framework that can implement some react and eventually replace it with some html like framework to display things on server into pages. Microsoft forcing most users even ones limited to mac os to use razor pages on visual studio but its possible to just use the server side.
I have a question. How do you rate Blitz?
The short answer is "no, react is not dying, but it should". Effectively it's a legacy tool. No reasonable SFC styling solutions, platform events replaced by synthetic events like it was jQuery. No new projects should be started on React in 2023.
You may have misread the chart. At the moment when you said "Angular is dying" is was actually showing increased awareness. It was just ranked lower because there were a bunch of newer frameworks in the ranked list.
Angular appears to be experiencing a renaissance.
i hope so, i recently graduated and like angular a lot more than the others haha,
xD
If React being "low level" were an advantage, then C++ or Assembly would still be the dominant programming languages.
Uhm... C++ is still a dominant programming language.
Sure it's not the new hot thing but every year a big portion of developers that work with C++ retire that needs replacing with new talent. It's going nowhere and will probably get a new boost in the future when people jump to the next hot thing which happens to involve c++.
Server Components are a game changer feature for fetching data and handle errors!!
Hey, it's seems like u have a new 7 string guitar :) What's the model?
Literally building with REACT on WordPress as I watch this video. 😄
What won’t die for sure is that God damn hair piece!
Yes and that’s okay, so many things are easier in frameworks like svelte or even vue, we should always use the best tool for the job, not the one most popular. Also as a developer you should be able to use any framework to do the job. If you only know how to do thing X in angular, you should invest time in learning other tools.
Thanks for sharing. Where do I find the data on retention? Is it the SO survey?
Nothing is replacing React soon. Because business always pick React. Switching would cost a fortune.
I think the React team is doing a few things in the last couple years that do not represent evolution or are not good at all (like all the logic behind hooks and their names, and their "rules"), specially because many things there are not intuitive, which is the opposite you expect as a developer. Other example is that React is always introducing new concepts and throwing everything you learned in the trash - for example the changes in the react-dom api and everything about class components.
Solid seems to be a great deal in comparison to React and other great simpler frameworks like Vue and Svelte, and it leverages the best thing in React in my opinion: JSX - and still has a nice simplicity as Svelte does. Looking forward to experiment that in a future project. For now, long live to React.
React was never meant to be intuitive, the first mistake beginners always do is try to mutate state directly because that's the intuitive thing to do and its wrong
If you haven't already, can you make a video explaining the differences between a framework and a library (like next or vite) please?
What is wrong with Angular ????
React is just a bad framework, hate it.
What do you think about solidjs?
And blazor wasm?
Hi, could you describe where you got these statistics? What program, that you use in this video?
0:42 every time I hear this I think I'm playing Rec Room paintball
This truly is a Javascript moment
Even if React stops being number 1... that just means it's number 2. Being number 2 is still very popular when it comes to frameworks in JS.
The great facts about it is react make ur chance to get money more coz company won't leave it
Nice graph. Where can I interact with this graph? Any link for it?
AI replacing devs is a bigger worry than one framework replacing another
that will legit never happen. don't be scaremongered into thinking AI will replace devs because ChatGPT can spit out code it found on the internet.
Where I find this graph ,do you know anything about solidjs vs qwik? what do you prefer over react and why? thank you for share .
Svelte is nice, but I wanna write JSX and I think SFCs are a regression
Okay, I love you man and I'll watch this video later. But I don't know if this is a click-bait or not (since it's a question). But the answer is no.
React is not going anywhere, anytime soon. It's probably one of the most frame (or rather libraries out there) followed my Angualr and Vue. Even the Vuestorefront which is a Nuxt framework for vue, has adapted the usage for React as well.
Tesco Tech, one of the largest retail markets in the world uses React For their ENTIRE platform
ICF and most streaming industries
Zeiss is currently moving it's B2B stack from Angular to React (I interviewed with them this year)
Just lookup on Indeed and Linkedin, React is relevant and is not going anywhere
instead of trying to learn a thousand frameworks, people should get themselves familiar with CI/CD, Docker, Cloud basics, Devops in general because that shit is spreading like wildfire. I'm serious. Good God, DevOps should be it's own profession, why the fuck are Frontended engineers required to master it!
Also in terms of PHP, a lot of people used to say that it's dead.... but PHP is still widely used
The same goes for Mainframes, people keep saying they'll die, but there doesn't exist a single computing device that can compute mainframe speed or security. No they're not dead but the older generation is retiring and it's not taught in Universities which is bad.
Even people who says cloud is replacing servers...... Don't realize that cloud is basically a network of servers? You're just not owning your own servers but rather renting out servers... like owning a house vs renting an apartment.
No React is not going anywhere, nor will it.
React's robust library and community support is a result if its popularity not a representation of its superiority.
What I don't like about the graph (0:52 - 4:30) is that it does a poor job of presenting the trends. Whenever a new framework is introduced, all other frameworks get pushed down, making the existing ones appear to be losing popularity.
For example, Svelte in 2020 was showing 89% and "dropped" to 90% in 2021 to make way for Solid.
I understand that each annual column just stacks the items top to bottom, most to least popular. I just think it could have been presented in a less confusing way.
How come % in the usage chart not added up to 100%?
shared this video on linkedin, nice !! Thank you Kyle
I don't know how should I feel about Emberjs having even 17%...
Software languages or frameworks increase abstraction as they mature and add features and new ones are released with less abstraction and less overhead.