Yea, but when current projects will switch to a newer version? It looks like businesses are not eager to update angular to modern versions. There are a lot of 12-14 versions out there on the job market.
I've worked with React for around six years, but I often find that handling state and hooks can overwhelm developers, especially when adding Redux or Context API just to share some simple data. In React, constantly managing re-renders can be a headache, whereas Angular's services make this process much more straightforward. That said, I love React, which is why I use React Native. For enterprise applications like ERP systems or similar software, Angular is my go-to choice. However, when it comes to mobile development with the goal of reusing code for the web, you need to move into the React world with React Native.
there is an approach which called micro front-end that allows us to build the application with different frameworks so get start from what you like to do. I really like Angular as its opinionated, a group of high experienced people at Google set out to design how something should work, and of course they have good choices based on their experience.
So many companies try to control React. They create base libraries and try to enforce developer coding styles. All this creates a lot of overhead that simply isn't maintainable. I've started several enterprise-level apps where a good part of my coding was creating complex wrappers to translate the requirements from UI to framework. They also institute broad system requirements such as using Redux for all state changes, which just adds layers of maintenance for not good reason. Even my first Angular project in 2018 had really good guidance from Angular without that many pitfalls. I also find testing Angular apps to be much easier because you don't need to deal with hooks and mocking is straight forward (similar to using Moq-like C# API testing). However, with the inclusion of NextJS and React Native, React does have a place in an enterprise if you can make use of server-side rendering or need a mobile solution.
SSR also works perfectly in Angular. Even Server-rendered Components will ship soon (19 or 20). However, when you want native apps React definitely has the edge. I personally don't see the point in Native apps, but I understand businesses need them because most users have been educated (mainly by Microsoft, Apple & Google) that native Apps are a good choice.
As amusing as this romanced opinion of both frameworks may be, the fact of the matter is that React does better with simpler applications, where as Angular thrives in enterprise level complexity. If you are dealing with huge complex legacy riddled applications or application suites, Angular keeps its shit together because it offers the structure to do so. You can create your own structure in React as well, but that comes at a cost of time (which equals money, in the real world).
I just started studying Angular after 2.5 years of react and nextjs.. I've seen my fair share of spaghetti code in my previous agency and I'm looking for stability. I also have the feeling that career wise Angular might be better to grow. Time will tell, maybe I'm going in the wrong direction.
I've worked with both react and angular for work for many years. Tbh there's usually more spaghetti in the angular projects due to the obsession with observables and devs not understanding how to use them in a neat way. Most react components are about 50-100 lines long, the angular components are often hundreds of lines long. I think part of this is how easy it is to extract react components out into smaller components. With angular it's much more involved to extract logic and templating code into their own components. JSX is a really nice way to write templates too, the angular templating system n comparison is a horrible dx. Angular is fine. Lots of enterprise clients still use it. The arguments for "structure" don't really hold weight, but it's convinced a lot of people who parrot that line. Angular is also improving, signals are a great step towards reactivity. It's worth learning just to be exposed to other ways of doing things, and learning how observables really work is useful. For my latest project where I i had carte blanch i picked nextjs and it's been a delight to work with. This is despite me spending more time writing much more angular for the last few years than react. Take that as you will.
I code with React and Angular. I’ll say my previous Angular experience has helped me comment my React code effectively before passing on to my teammate. They both have their pros and cons. I’ll be picking up Vue later since one of our apps is moving to that framework. Good video.
I have been a frontend engineer for almost a decade now. I have used Angular and React almost 50/50 during that time and I would say I mostly do NOT agree with you. Both frameworks are equally versatile and with the same capabilities. I don't see anything you can do in React that you cannot do in Angular and vice versa. The real differences between the frameworks are the level of structure out of the box where Angular is way more opinionated and has a more solid initial structure, the way they handle data - Promises vs RxJS (now Signals) where React used to be a lot more simple due to the extremely high learning curve of RxJS and the final difference Angular's dependency injection vs the React store where in my opinion it is only preference that makes the difference. All in all both are sound frameworks with huge communities and both are worth learning. Angular market is a bit smaller due to historical reasons so I would say React will land you a job faster.
Actually Angular used to be neck and neck with React (and even ahead when it was AngularJS, if you look at Google Trends) so I'm not sure I understand why you say they have a smaller share for historical reasons ?
I had work with Angular for 12 years, now that I'm looking for a new job. 90% of the open positions require React, Node.js and Next.js or Remix. About 10% of new jobs require Angular, so in my opinion Angular is loosing relevance on the job market.
I actually started coding in Angular first, then learn React when it changed to a more functionnal style of programming. And it wasn't too difficult to get my head around things. Your best bet (both on the job market, and for your growth as a programmer) is probably to know both :)
I think it all depends on your skills. I can see why lots of people tend to prefer Angular because it works in a certain way out of the box. Personally I prefer to get some pieces and then think about how they fit best for the next project.
I love your video! Don't get why React leads to a better UX though. So many factors play into UX. If you mean performance wise. Then I think that is an already outdated point of view.
I definitely agree on your POV regarding use-cases. I left big companies and ESNs a while ago and technically I also shifted from Angular to React. Most startups and small companies use React. I find much more freedom in the React ecosystem. I also find that React is the go-to framework for frontend development newbies. It has lots of good packages and tools you can use. I'm now keeping an eye on the more recent frameworks, such as Vue, SolidJs, Svelte, etc. which bring lots of new features and paradigms to the table. So far, Angular and React try to keep up on the pace by borrowing new concepts from them. Signals are part of this run. We'll see if signals are a game changer, but their adoption plan by ecmascript might make it generic in all frameworks 😁 My two cents would be to stay strong on the basics of frontend development and stay open to any framework.
It's like Java and PHP. Depending on whether or not it's intended for enterprise use where structure, robustness, testability, security, maintainability, etc are needed.
This would be in a rather rare case when you need to push the application to its limits, eg in terms of performance or rendering, where the opinionated nature of Angular would end up making things a lot more difficult. This is an extreme case though, which is why I used the term “exceptional” :)
@@KodapsAcademySo, in other words you've got no clue about Angular. Your vague and empty phrases are so telling. Good to know that you can be a senior and still a clueless doorknob.
Would have been helpful to explain that a bit more in the video, your fast food metaphor made it sound like Angular could only do mediocre quality because fast food is really low quality. It was a pretty bad metaphor.
@@GnarledStaff dont even bother man, this kind of channel is just about the last trend with superficial content just for clicks, you cant really take serious "tech influencers". Its all about this vs that, and why I change from this to that etc...
Loved the quality of the video. I didn't learn any of those fancy JS libraries/frameworks yet (except jQuery, lmao). And honestly i am left with more questions than answers. It's a gamble somewhat at least. I consider myself a fresh freelancer and i was thinking about creating my own website and at the same time learn something new alongside that process. I wouldn't generally say this, but in the case of tech stuff i would definitely trust Google more than FB/Meta, even if React is more popular. Even if i am not gonna make banking websites, i think it's better long term to start off with Angular and it's stricter rules and then transition over to learn React. This way i hope i would write less spaghetti :D Anyway, thank you! Writing this comment also somewhat sorted my thoughts, which wasn't really intended. :D
I’ve had positions with react, vue, and now angular. I must say angular is more production ready and built for enterprise In the beginning of my career I would have said react but people forget that react is a library and a paradigm (at least these days). Too many libs and configurations for me to get things rolling. With vue and angular you get a full fledged framework with opinionated design patterns and robust APIs. Angular is naturally modular out of them all too imo If I’m prototyping with no intention to ship to real users or looking to have fun doing a side project vue or react but for something serious I’ll be using angular for sure
Great video, I've worked with both, is curious because I used angular to create a startup project from scratch it was good because I wanted to get all the opinions done given it was my first esperience using a frontend framework, and I've worked using React with large teams and for large companies and it could be really complicated to unsderstand what was happening in the head of the dev that created that component. At the end of the day this video resumes very well both frameworks.
React needs 10 libraries before becoming useful. React also promotes code now error later. Angular by far is better than React. Popularity is not equivalent to quality. There are millions of noob developers out there that dont want to use Angular because it impose quality and maitainable code that noob developer hates. Sorry to say many React devs dont know how code with quality.
This comment strikes me as biased. While it's true that React encourages diverse coding styles, it's important to note that this evolution is a natural result of the framework and community's growth. Moreover, React has consistently demonstrated excellent compatibility and codemod support, allowing for seamless migrations to newer versions with minimal hassle. In contrast, Angular has a history of poor backward compatibility, leaving many projects stuck on Angular 1 due to the significant rework required to upgrade to newer versions.
@@u2blr Your argument that there are many projects stuck in Angular is a decade years old now. Most of those projects already upgraded to Angular 2+. Unlike ReactJS every version they release right now will surely breaks existing libraries that you are using. Angular2+ to Angular17 is backward compatible unlike ReactJS 16 and React17 that breaks a lot of existing React projects. I know this because I experience it with React.
@@KodapsAcademy Like I said noob developer will have a hard time with angular. There is a cli command to update angular. I am 100% sure you dont use Angular.
Since angular introduced signals, the argument that react has a simpler mental model no longer holds. React has a beautiful mental model (functions taking data and spitting out markup). However signals model the chaos of ui much more elegantly. Reading stacktraces in react is not a nice experience, hooks are really obscure and esoteric, and the fact that no react projects look alike... That's not good. I will gladly sacrifice some control over my ecosystem if i can just hit the ground running like i do when i start a new angular project. With react, i have the agony of choice and the anxiety that some of my 3rd party libraries would die out in 2 years or that my taste in library might displease other devs.
I've found out about your channel just now (in addition to your French channel). Gosh, your English is just right on point. Where did you learn it? From school or do you have family back in the UK?
English is my mother tongue (and I was born in the UK), but my parents moved to France when I was 5 and I did all my studies in the French school system :)
@@KodapsAcademy I thought so! If I may ask: where in the UK? I struggle to locate your accent 🤔 I would say somewhere in the south but not 100% sure where 😅
@@JulienCassin-lv4yi my accent was informed by listening to BBC Radio 4 on AM radio quite a bit, but my family is from Cheam (south of Wimbledon) , Aldershot and Guilford (between London and the south coast) :)
I strongly disagree with your conclusion that react is more agile and that as a startup with a small team you inevitable have to go with react. Especially small startups might not have the highly skilled react developers that are needed to not build garbage code, which by the way also takes time to build, setup, align on and so on. you can at any time throw some average Angular developers into a project and they know what they see and where, whereas with react you have to learn the lead developers opinion, taste and so on; or even worse the one person's decision, who is no longer in the company. Lastly the you can't build everything with Angular statement is bewildering to me, as I don't know of any app, that couldn't have been built with Angular, not saying it is always the right choice (or vice versa react) Last but not least I want to say it really depends on what you want to build. E.g. Angular is rarely a good choice for a blog.
I guess it would be mindset, and ease of doing what you want. Like sure you can more easily make reusable components in React than in Angular, but what stops someone from making an angular module just for reusable components like custom buttons. I mean, how else do libraries like Material exist for Angular and React.
"React is not opinionated". I always found this line to be largely false. Each and every react app is different - hence they have more opinions than everyone else. In terms of quality, you can write bad code in both, its just that, the tendency in angular is you write bad code following angular's MVVM. One thing I've noticed though is, as your react app grows and requires more structure and consistency, it tends to look like an angular based-app.
"Each and every react app is different" is *precisely* what I mean when I say that React itself is not opinionated. Being opinionated, when talking about a library or framework means it imposes its opinion on everyone else, which limits the range of developper's options and opinions.
Miguel, U know what "Opinionated" and "unopinionated" in framework or Library context? Opinionated means it is already have opinion by its author which is like structure, flow, pattern, etc by the author and unopinionated is people who use it is free to write their own flow, structure, etc. Example : express js is unopinionated, laravel is Opinionated
@@policeislam2846 They don't use the same react library that we use, think about that. And they combine it with a lot of libraries and tool that you can't afford, so they can create a big app. If we use react, we install libraries like react router and others xD from npm wich has a lot of problems. So, creating a big app with react is a nightmare for us, we need solutions like Angular wich has all the features that we need.
@@policeislam2846 Not generally comparable. One Sr. software person at one of those companies probably makes as much as the entire dev team at most of the small teams using React. There aren't enough really great developers to go around so many teams make many mistakes along the way and companies are left detangling the spaghetti until ultimately the code base is either dropped or another company is purchased because they ruined the last one.
React is somewhat of a mess recently, with it's own documentation pointing you towards full-application-frameworks like nextja and having had no stable release for almost 2 full years from 2022 to 2024. Meanwhile nextjs was using unstable versions of react and introduced massive bugs into their own "stable" releases. How the hell did it become like this? Compare that to Angular. That moves with Lightspeed und will be su much better a year from now with signal-based-components and "zoneless". State of JS does not really represent the market all that well. As you said Angular devs are usually in pretty stable environments and teams and mostly dont participate with other frameworks (or "state of js"). The best indication are job trends imo, which puts React comfortably in front in most regions, though Angular is slightly ahead in Europe.
Angular is an Enterprise full-framework, and React is just a library. In our company we made sure we never hire any developers who make decisions based on social media. Because such developers don't know shit about Software Development and they do whatever they watch on the internet without even testing and understanding it themselves. Such people can bring thousands of dollars costs of re-writing the whole software, of course after some months when the codes and infrastructure start to show themselves how bad they are. Simple App => React Enterprise Apps (especially for Organizations and Internal Apps) => Angular
Like I said in another video, I agree that if your developers are all junior (and it looks like it if you're basing hiring decisions on if devs listen to social media :) ) it's best to go with the structure Angular provides, and probably safer. But with senior devs to provide structure, React can work well in an Entreprise environment.
3:59 MacDonald's is a poor choice for making the quality comparison. Have you seen their 'value menus'? High prices for very little, and you still get stuck with obesity and diabetes for your trouble.
Very well spoken, but you miss the point. React is a library Angular is a framework. You (and many other ppl) compare apples with pears.. Compare Nextjs, Remix or whatever with Angular. That works. But this comparison is of no real use.
@@KodapsAcademy I understand your point, but what React and its evolution is doing is nothing more than making the library easier for frameworks and devs to use. From my perspective React is still far away from being a framework itself like angular is.
Comparing Angular to McDonalds is where you lost credibility here IMO... you can say a lot of things, but quality code is better than react bc the app is made for enterprises
My point was not that the quality was poor, but that it is in a narrower band and a known quantity. You know what you’re getting, basically. Kind of like a fast food franchise :)
@@KodapsAcademy Still very poor analogy in my opinion because I can say the same thing about restaurants I usually visit where I know what I'm getting. I was genuinely confused when you said that in the video because it's the complete opposite in my head, Angular gives you more to work with, more structure and stability whereas React is more fast paced, agility as you mentioned many times throughout the video.
Think of it more as the owner than the customer. Would you rather own mcdonalds or a bunch of resturants doing their own thing and different structures. One is more consistent than the other
@@Tropax1 Bro i will be honest he did the correct analogy here, you are just biased, i feel like angular is similar to large food chains they are stable and move at very slow paces cause they have to think about if the changes would break large organization, which mcdonalds or any huge chains would be wary of , whereas React is like that one restaurant where you know you have to pay lot but you know there are some returns ,based how the developers implement the solution, and thats the beauty we have so many libraries that help react become so useful like shadcn ui and other competitive frameworks like remix and next js that these compared to how angular is moving is too slow and makes angular very dumb to be competing with fast bunch of meat heads who are trying to win it , I believe angular is the professor who takes calculated way of coding where the chances of breaking is very minimal but that is also a disadvantage it is not highly competitive . It cannot be just picked up by a junior dev.
@@Divineleo2023 You went out of your way to tell me how react is better and you're calling me bias? Really?? There's a reason enterprises prefer Angular.
React is amazing because today you are not nesserly using normal react you are using next.js witch is very good and reliable and very quick to start witch But the idea that you write bad code is simply not true because its depends on the developers and this is why you have a team lead
Arguments like React is chaotic or Angular is for enterprise are total nonsense. Projects are as chaotic as the developers working on them. I have seen dozens of brutally chaotic and artificially complex projects in both camps. If you assume professional, competent developers, more choices and more freedom are good things. What is much more important about a piece of tech is how productive you can be with it and whether it fits the goal and the people.
If you are going to nitpick please make sure you understand the point being made :) I did not say that there exists a framwork that has a new release every week, but that every week it seems like a new framework is released / announced. Which is why there is such a thing as JavaScript framework fatigue and websites like this one: dayssincelastjavascriptframework.com/
React is unopinionated. It's like a very sharp and powerful knife that one can easily cut themselves with. If you use it poorly, it'll yield a bad product. Angular is very structured and contained, but I don't care for the syntax and functionality. I've been using React since its Beta phase and it has always been my go-to. I'm glad React 19 finally on its way.
Also, Angular was NOT released in 2016, it was Angular 2 which was released back in 2016. Full of mis-information, you know it's a crime to spread one?
Felt like I just watched a high quality 40 mins documentary on React and Angular !!!!!
React for the hype. Angular for long term scalable products.
Spot on!
Angular with signals is the way 🙌
Yea, but when current projects will switch to a newer version? It looks like businesses are not eager to update angular to modern versions. There are a lot of 12-14 versions out there on the job market.
What if JavaScript brought in signals? would it matter to you which framework you used?
don't forget nx
Yeh, it's amazing.
This this this. Signals have completely changed the game in my opinion.
I've worked with React for around six years, but I often find that handling state and hooks can overwhelm developers, especially when adding Redux or Context API just to share some simple data. In React, constantly managing re-renders can be a headache, whereas Angular's services make this process much more straightforward. That said, I love React, which is why I use React Native. For enterprise applications like ERP systems or similar software, Angular is my go-to choice. However, when it comes to mobile development with the goal of reusing code for the web, you need to move into the React world with React Native.
there is an approach which called micro front-end that allows us to build the application with different frameworks so get start from what you like to do. I really like Angular as its opinionated, a group of high experienced people at Google set out to design how something should work, and of course they have good choices based on their experience.
One of the best comparison I've heard ever for this topic .. Thank you
So many companies try to control React. They create base libraries and try to enforce developer coding styles. All this creates a lot of overhead that simply isn't maintainable. I've started several enterprise-level apps where a good part of my coding was creating complex wrappers to translate the requirements from UI to framework. They also institute broad system requirements such as using Redux for all state changes, which just adds layers of maintenance for not good reason. Even my first Angular project in 2018 had really good guidance from Angular without that many pitfalls. I also find testing Angular apps to be much easier because you don't need to deal with hooks and mocking is straight forward (similar to using Moq-like C# API testing). However, with the inclusion of NextJS and React Native, React does have a place in an enterprise if you can make use of server-side rendering or need a mobile solution.
SSR also works perfectly in Angular. Even Server-rendered Components will ship soon (19 or 20). However, when you want native apps React definitely has the edge. I personally don't see the point in Native apps, but I understand businesses need them because most users have been educated (mainly by Microsoft, Apple & Google) that native Apps are a good choice.
As amusing as this romanced opinion of both frameworks may be, the fact of the matter is that React does better with simpler applications, where as Angular thrives in enterprise level complexity. If you are dealing with huge complex legacy riddled applications or application suites, Angular keeps its shit together because it offers the structure to do so. You can create your own structure in React as well, but that comes at a cost of time (which equals money, in the real world).
I just started studying Angular after 2.5 years of react and nextjs.. I've seen my fair share of spaghetti code in my previous agency and I'm looking for stability. I also have the feeling that career wise Angular might be better to grow. Time will tell, maybe I'm going in the wrong direction.
I've worked with both react and angular for work for many years. Tbh there's usually more spaghetti in the angular projects due to the obsession with observables and devs not understanding how to use them in a neat way.
Most react components are about 50-100 lines long, the angular components are often hundreds of lines long. I think part of this is how easy it is to extract react components out into smaller components. With angular it's much more involved to extract logic and templating code into their own components.
JSX is a really nice way to write templates too, the angular templating system n comparison is a horrible dx.
Angular is fine. Lots of enterprise clients still use it. The arguments for "structure" don't really hold weight, but it's convinced a lot of people who parrot that line. Angular is also improving, signals are a great step towards reactivity. It's worth learning just to be exposed to other ways of doing things, and learning how observables really work is useful.
For my latest project where I i had carte blanch i picked nextjs and it's been a delight to work with. This is despite me spending more time writing much more angular for the last few years than react. Take that as you will.
Thank you for your answer :)
combining angular with nx will help you with setting up an awesome structure
@buzz1ebee you described a terrible angular codebase.
what you described is not the framework, but rather the devs.
Thank you for this video. With signals and zoneless angular is th best for me 👍
I code with React and Angular. I’ll say my previous Angular experience has helped me comment my React code effectively before passing on to my teammate. They both have their pros and cons. I’ll be picking up Vue later since one of our apps is moving to that framework. Good video.
I've worked with angular and vue, but vue (2) was so bad
I have been a frontend engineer for almost a decade now. I have used Angular and React almost 50/50 during that time and I would say I mostly do NOT agree with you. Both frameworks are equally versatile and with the same capabilities. I don't see anything you can do in React that you cannot do in Angular and vice versa. The real differences between the frameworks are the level of structure out of the box where Angular is way more opinionated and has a more solid initial structure, the way they handle data - Promises vs RxJS (now Signals) where React used to be a lot more simple due to the extremely high learning curve of RxJS and the final difference Angular's dependency injection vs the React store where in my opinion it is only preference that makes the difference. All in all both are sound frameworks with huge communities and both are worth learning. Angular market is a bit smaller due to historical reasons so I would say React will land you a job faster.
Actually Angular used to be neck and neck with React (and even ahead when it was AngularJS, if you look at Google Trends) so I'm not sure I understand why you say they have a smaller share for historical reasons ?
@@KodapsAcademy Angular 2+ is basically a different framework than AngularJS and came out in 2016. React came out in 2013, so it had a head start.
React is not a framework
angular is just a boilerplate shit. If you are someone who likes to learn new things, angular is not for you. Even tailwind support came too late.
@@cenkakay3506 new things are for tutorials and demos, for production you should use a solution, like Angular wich has everything.
React was initially released on May 29, 2013 and not in 2011 as mentioned in the video. It was Angular 1's era back then.
This is the best explained video on youtube.... Angular vs React.
I had work with Angular for 12 years, now that I'm looking for a new job. 90% of the open positions require React, Node.js and Next.js or Remix. About 10% of new jobs require Angular, so in my opinion Angular is loosing relevance on the job market.
but in react you have greater competition to get a job. So you need to be an exceptional programmer to stand out
@@marcossouzajr1711after understanding angular and rxjs, it's not that difficult to switch to react imo.
Fact
I actually started coding in Angular first, then learn React when it changed to a more functionnal style of programming. And it wasn't too difficult to get my head around things. Your best bet (both on the job market, and for your growth as a programmer) is probably to know both :)
That's a fair assessment. I really like Angular, having used it since 2014. React is one I want to learn. Wiz sounds very interesting. Thank you
Just discovered your channel. I like your video style. Subscribed!
Thanks, and welcome aboard !
Thanks for the video! It has clear explanation when and why chose Angular/React.
I think it all depends on your skills. I can see why lots of people tend to prefer Angular because it works in a certain way out of the box. Personally I prefer to get some pieces and then think about how they fit best for the next project.
I love your video!
Don't get why React leads to a better UX though. So many factors play into UX.
If you mean performance wise. Then I think that is an already outdated point of view.
I definitely agree on your POV regarding use-cases.
I left big companies and ESNs a while ago and technically I also shifted from Angular to React. Most startups and small companies use React.
I find much more freedom in the React ecosystem.
I also find that React is the go-to framework for frontend development newbies. It has lots of good packages and tools you can use.
I'm now keeping an eye on the more recent frameworks, such as Vue, SolidJs, Svelte, etc. which bring lots of new features and paradigms to the table.
So far, Angular and React try to keep up on the pace by borrowing new concepts from them. Signals are part of this run.
We'll see if signals are a game changer, but their adoption plan by ecmascript might make it generic in all frameworks 😁
My two cents would be to stay strong on the basics of frontend development and stay open to any framework.
thanks for your input!
I think React with the much bigger community, extensions and the new compiler update will be a save bet.
It's like Java and PHP. Depending on whether or not it's intended for enterprise use where structure, robustness, testability, security, maintainability, etc are needed.
Could You care to elaborate why someone can not create a "exceptional" application with angular?
This would be in a rather rare case when you need to push the application to its limits, eg in terms of performance or rendering, where the opinionated nature of Angular would end up making things a lot more difficult. This is an extreme case though, which is why I used the term “exceptional” :)
@@KodapsAcademySo, in other words you've got no clue about Angular. Your vague and empty phrases are so telling. Good to know that you can be a senior and still a clueless doorknob.
Would have been helpful to explain that a bit more in the video, your fast food metaphor made it sound like Angular could only do mediocre quality because fast food is really low quality.
It was a pretty bad metaphor.
@@GnarledStaff dont even bother man, this kind of channel is just about the last trend with superficial content just for clicks, you cant really take serious "tech influencers". Its all about this vs that, and why I change from this to that etc...
@@KodapsAcademy yeah that was poor comparison
Thanks for this. It was honestly amazing
I’m glad you liked it :)
Valuable infos. Perfect ambiente. Above a huge hidden experience. 👍
Loved the quality of the video. I didn't learn any of those fancy JS libraries/frameworks yet (except jQuery, lmao). And honestly i am left with more questions than answers. It's a gamble somewhat at least. I consider myself a fresh freelancer and i was thinking about creating my own website and at the same time learn something new alongside that process.
I wouldn't generally say this, but in the case of tech stuff i would definitely trust Google more than FB/Meta, even if React is more popular. Even if i am not gonna make banking websites, i think it's better long term to start off with Angular and it's stricter rules and then transition over to learn React. This way i hope i would write less spaghetti :D
Anyway, thank you! Writing this comment also somewhat sorted my thoughts, which wasn't really intended. :D
I've bern waiting for this video, thank you.
Glad you liked it :)
I’ve had positions with react, vue, and now angular. I must say angular is more production ready and built for enterprise
In the beginning of my career I would have said react but people forget that react is a library and a paradigm (at least these days). Too many libs and configurations for me to get things rolling.
With vue and angular you get a full fledged framework with opinionated design patterns and robust APIs. Angular is naturally modular out of them all too imo
If I’m prototyping with no intention to ship to real users or looking to have fun doing a side project vue or react but for something serious I’ll be using angular for sure
Great video, I've worked with both, is curious because I used angular to create a startup project from scratch it was good because I wanted to get all the opinions done given it was my first esperience using a frontend framework, and I've worked using React with large teams and for large companies and it could be really complicated to unsderstand what was happening in the head of the dev that created that component. At the end of the day this video resumes very well both frameworks.
Enormously helpful. Thank you.
Glad to be of service :)
React needs 10 libraries before becoming useful. React also promotes code now error later. Angular by far is better than React. Popularity is not equivalent to quality. There are millions of noob developers out there that dont want to use Angular because it impose quality and maitainable code that noob developer hates. Sorry to say many React devs dont know how code with quality.
This comment strikes me as biased. While it's true that React encourages diverse coding styles, it's important to note that this evolution is a natural result of the framework and community's growth. Moreover, React has consistently demonstrated excellent compatibility and codemod support, allowing for seamless migrations to newer versions with minimal hassle. In contrast, Angular has a history of poor backward compatibility, leaving many projects stuck on Angular 1 due to the significant rework required to upgrade to newer versions.
@@u2blr Your argument that there are many projects stuck in Angular is a decade years old now. Most of those projects already upgraded to Angular 2+. Unlike ReactJS every version they release right now will surely breaks existing libraries that you are using. Angular2+ to Angular17 is backward compatible unlike ReactJS 16 and React17 that breaks a lot of existing React projects. I know this because I experience it with React.
@mac.ignacio upgrading Angular isn’t without its difficulties either … (I’m not talking about AngularJs) :)
@@KodapsAcademy Like I said noob developer will have a hard time with angular. There is a cli command to update angular. I am 100% sure you dont use Angular.
Sure, be 100% sure if you want :D
This was the most relaxing video i've ever watched on youtube
Thanks ! :)
Been using sencha extjs for years, not even on the lists here.. think angular would be easiest to migrate to being similar in scope
Great pacing in the video, with an interesting hook
Thanks for this! How about if I really need a job and I don't know how to compete with the 10,000,000 react developers who apply to every job?
I should saw this video 2 years ago. I'm an oipinionated dev.
Thanks for the video.
Since angular introduced signals, the argument that react has a simpler mental model no longer holds. React has a beautiful mental model (functions taking data and spitting out markup). However signals model the chaos of ui much more elegantly. Reading stacktraces in react is not a nice experience, hooks are really obscure and esoteric, and the fact that no react projects look alike... That's not good. I will gladly sacrifice some control over my ecosystem if i can just hit the ground running like i do when i start a new angular project. With react, i have the agony of choice and the anxiety that some of my 3rd party libraries would die out in 2 years or that my taste in library might displease other devs.
Objective fact: Angular is the GOAT
You have a very rhythmic way of talking. It's soporific.
Thank you for your kind words, I'm glad I found grace in your eyes (and ears)!
Great comparison! As a newbie starting out I'd recommend React as there are so much more resources geared to learning it.
Yea but how much of it is up to date? Utter chaos
Should I learn react or angular?
Touched both for long time trying to avoid Angular projects.. at the end of the day
Nice video , I have startup ., i want to make something like AI powered Special video editor fully in browser , which is better for stability ?
pick either one, stability depends on your devs.
A very helpful comparison!!
Glad you liked it :)
The volume level is messed up in this video.
I've found out about your channel just now (in addition to your French channel). Gosh, your English is just right on point. Where did you learn it? From school or do you have family back in the UK?
English is my mother tongue (and I was born in the UK), but my parents moved to France when I was 5 and I did all my studies in the French school system :)
@@KodapsAcademy I thought so! If I may ask: where in the UK? I struggle to locate your accent 🤔 I would say somewhere in the south but not 100% sure where 😅
@@JulienCassin-lv4yi my accent was informed by listening to BBC Radio 4 on AM radio quite a bit, but my family is from Cheam (south of Wimbledon) , Aldershot and Guilford (between London and the south coast) :)
Great comparison 🔥🔥
Thanks !!
For me, if I want to start a new project, neither of them is a choose. They will works, and do the job, but there is just a better players now imo.
Loved the way you explained man!
Thanks :)
Video very well made. Could you talk about javascript metaframeworks?
I strongly disagree with your conclusion that react is more agile and that as a startup with a small team you inevitable have to go with react.
Especially small startups might not have the highly skilled react developers that are needed to not build garbage code, which by the way also takes time to build, setup, align on and so on. you can at any time throw some average Angular developers into a project and they know what they see and where, whereas with react you have to learn the lead developers opinion, taste and so on; or even worse the one person's decision, who is no longer in the company.
Lastly the you can't build everything with Angular statement is bewildering to me, as I don't know of any app, that couldn't have been built with Angular, not saying it is always the right choice (or vice versa react)
Last but not least I want to say it really depends on what you want to build. E.g. Angular is rarely a good choice for a blog.
Great content. Thanks for doing this!
i love how its explained
Thanks :)
I don't understand why react would be better for UX, neither of them limits what the designer can or cannot do.
I guess it would be mindset, and ease of doing what you want. Like sure you can more easily make reusable components in React than in Angular, but what stops someone from making an angular module just for reusable components like custom buttons. I mean, how else do libraries like Material exist for Angular and React.
Thank u!
Excellent analysis
Why not Both of them ? ? ?
That was really good!
Thank you very much :)
"React is not opinionated". I always found this line to be largely false.
Each and every react app is different - hence they have more opinions than everyone else.
In terms of quality, you can write bad code in both, its just that, the tendency in angular is you write bad code following angular's MVVM.
One thing I've noticed though is, as your react app grows and requires more structure and consistency, it tends to look like an angular based-app.
"Each and every react app is different" is *precisely* what I mean when I say that React itself is not opinionated. Being opinionated, when talking about a library or framework means it imposes its opinion on everyone else, which limits the range of developper's options and opinions.
Miguel, U know what "Opinionated" and "unopinionated" in framework or Library context? Opinionated means it is already have opinion by its author which is like structure, flow, pattern, etc by the author and unopinionated is people who use it is free to write their own flow, structure, etc. Example : express js is unopinionated, laravel is Opinionated
You mesmerized me 🎉
@@DemystifyFrontend thanks :)
You can't compare library with framework. Compare Angular with Nextjs and thats fair because both are framework.
React call itself library but it is more than that but less than framework (like you can just set react vite project for full csr)
well explained 👏
2:40 its called controller - MVC
It is if you’re talking about Angular JS. Here we’re talking about Angular 2+ which does not have controllers per se.
React is a library, It's perfect for small apps. If you want to create a big app, the best choise is a framework like Angular.
Small apps like facebook or Instagram??
@@policeislam2846 They don't use the same react library that we use, think about that. And they combine it with a lot of libraries and tool that you can't afford, so they can create a big app. If we use react, we install libraries like react router and others xD from npm wich has a lot of problems. So, creating a big app with react is a nightmare for us, we need solutions like Angular wich has all the features that we need.
@@policeislam2846 it is used internally. this doesnt mean that FB developed with react. it is php dude
@@policeislam2846 Not generally comparable. One Sr. software person at one of those companies probably makes as much as the entire dev team at most of the small teams using React. There aren't enough really great developers to go around so many teams make many mistakes along the way and companies are left detangling the spaghetti until ultimately the code base is either dropped or another company is purchased because they ruined the last one.
i like this bold opinion
Thanks :)
Now nextjs vs angular please!
superb!
Thanks man
Glad to be of service :)
Compare NextJs with Angular
React is somewhat of a mess recently, with it's own documentation pointing you towards full-application-frameworks like nextja and having had no stable release for almost 2 full years from 2022 to 2024. Meanwhile nextjs was using unstable versions of react and introduced massive bugs into their own "stable" releases. How the hell did it become like this?
Compare that to Angular. That moves with Lightspeed und will be su much better a year from now with signal-based-components and "zoneless".
State of JS does not really represent the market all that well. As you said Angular devs are usually in pretty stable environments and teams and mostly dont participate with other frameworks (or "state of js").
The best indication are job trends imo, which puts React comfortably in front in most regions, though Angular is slightly ahead in Europe.
whats with the vsauce music? :S
I ❤ this video thanks
The question is: do you want a framework or not? That's it.
I prefer templating lol
I quit both 😮
Angular ❤❤❤
Angular is an Enterprise full-framework, and React is just a library.
In our company we made sure we never hire any developers who make decisions based on social media.
Because such developers don't know shit about Software Development and they do whatever they watch on the internet without even testing and understanding it themselves.
Such people can bring thousands of dollars costs of re-writing the whole software, of course after some months when the codes and infrastructure start to show themselves how bad they are.
Simple App => React
Enterprise Apps (especially for Organizations and Internal Apps) => Angular
Like I said in another video, I agree that if your developers are all junior (and it looks like it if you're basing hiring decisions on if devs listen to social media :) ) it's best to go with the structure Angular provides, and probably safer. But with senior devs to provide structure, React can work well in an Entreprise environment.
Was there a single line of code in this video?
Zoneless Angular
I would choose React over Angular. But I would choose HTMX over both.
svelte and react
I m using jQuery, and In some Rect projects I ve destractured the ajax module from jQuery
import { ajax } from 'jquery'
I m chaotic evil 🤣🤣🤣🤣🤣🤣
3:59 MacDonald's is a poor choice for making the quality comparison. Have you seen their 'value menus'? High prices for very little, and you still get stuck with obesity and diabetes for your trouble.
I keep hearing this guy mention agility, but what good is the agility when you need to rewrite your react components 20 times 😂 😂
This guy is wondering why exactly you find yourself needing to rewrite the react component 20 times ; it kind of feels like blaming your tools :)
Very well spoken, but you miss the point.
React is a library
Angular is a framework.
You (and many other ppl) compare apples with pears..
Compare Nextjs, Remix or whatever with Angular. That works. But this comparison is of no real use.
My point is precisely that with React 19, saying React is "just a library" has become significantly less true :)
@@KodapsAcademy I understand your point, but what React and its evolution is doing is nothing more than making the library easier for frameworks and devs to use. From my perspective React is still far away from being a framework itself like angular is.
Comparing Angular to McDonalds is where you lost credibility here IMO... you can say a lot of things, but quality code is better than react bc the app is made for enterprises
My point was not that the quality was poor, but that it is in a narrower band and a known quantity. You know what you’re getting, basically. Kind of like a fast food franchise :)
@@KodapsAcademy Still very poor analogy in my opinion because I can say the same thing about restaurants I usually visit where I know what I'm getting. I was genuinely confused when you said that in the video because it's the complete opposite in my head, Angular gives you more to work with, more structure and stability whereas React is more fast paced, agility as you mentioned many times throughout the video.
Think of it more as the owner than the customer. Would you rather own mcdonalds or a bunch of resturants doing their own thing and different structures. One is more consistent than the other
@@Tropax1 Bro i will be honest he did the correct analogy here, you are just biased, i feel like angular is similar to large food chains they are stable and move at very slow paces cause they have to think about if the changes would break large organization, which mcdonalds or any huge chains would be wary of , whereas React is like that one restaurant where you know you have to pay lot but you know there are some returns ,based how the developers implement the solution, and thats the beauty we have so many libraries that help react become so useful like shadcn ui and other competitive frameworks like remix and next js that these compared to how angular is moving is too slow and makes angular very dumb to be competing with fast bunch of meat heads who are trying to win it , I believe angular is the professor who takes calculated way of coding where the chances of breaking is very minimal but that is also a disadvantage it is not highly competitive . It cannot be just picked up by a junior dev.
@@Divineleo2023 You went out of your way to tell me how react is better and you're calling me bias? Really?? There's a reason enterprises prefer Angular.
React is amazing because today you are not nesserly using normal react you are using next.js witch is very good and reliable and very quick to start witch
But the idea that you write bad code is simply not true because its depends on the developers and this is why you have a team lead
Talk is cheap. Show me the code.
Video summarised: react is really bad only use it for you todo and use angular for real projects
Arguments like React is chaotic or Angular is for enterprise are total nonsense. Projects are as chaotic as the developers working on them. I have seen dozens of brutally chaotic and artificially complex projects in both camps. If you assume professional, competent developers, more choices and more freedom are good things. What is much more important about a piece of tech is how productive you can be with it and whether it fits the goal and the people.
You kind of missed the point. The “chaotic” was in the context of D&D alignment, not in the sense you seem to have taken it to mean.
@@KodapsAcademy What do you mean by D&D?
@n4bb12 Dungeons and Dragons (en.m.wikipedia.org/wiki/Alignment_(Dungeons_%26_Dragons) )
@@KodapsAcademy Oh, I didn't get that reference. Now it makes more sense.
Fair point but such developers aren't the common variety, generally available ones.
Please name at lest few JS frameworks that are released every week? huh???
If you are going to nitpick please make sure you understand the point being made :) I did not say that there exists a framwork that has a new release every week, but that every week it seems like a new framework is released / announced. Which is why there is such a thing as JavaScript framework fatigue and websites like this one: dayssincelastjavascriptframework.com/
React is unopinionated. It's like a very sharp and powerful knife that one can easily cut themselves with. If you use it poorly, it'll yield a bad product.
Angular is very structured and contained, but I don't care for the syntax and functionality. I've been using React since its Beta phase and it has always been my go-to. I'm glad React 19 finally on its way.
Both are not the best option. I would choose Vue. :P
Good for you :)
Angular is good for old folks react for new
Both suck ass compared to Svelte and Vue.
Also, Angular was NOT released in 2016, it was Angular 2 which was released back in 2016. Full of mis-information, you know it's a crime to spread one?
angularJS is totally different thing. like java vs javascript.
Stating that misinformation is a crime is incorrect which makes it … misinformation? :D
No react no angular, just need blazor
Hhhh
Vue is better than both