Vue: When you buy a car, you get a car. React: When you buy a car, you only get the chassis and engine. BYO brakes, exterior and interior, wheels, etc. Angular: When you buy a car, you get the car, the car dealership, the engineers, the salespeople, the technicians, and a complimentary petrol station. Buyer assumes all risks and operating costs.
Angular is like Visual Studio IDE - a billion icons and panes. Comparatively React is like VS Code - lightweight and you add just what you want (hence its popularity) lol
Vue - wheels possibly just the exhaust or seats React - wheels possibly just the exhaust or seats Angular - the entire, complete car - learn to drive it and only need one.
@Gus Erland Angular is designed for large project, giving your consistency and standardization so that you do not lose maintainability over time. the 3 major web frameworks all exists for a reason
@Gus Erland what you mentioned could be a reason but not all .. give you an example, for angular, there is one official way to do http request from very beginning. but in react, before it is official httpclient, you have a lot https client libraries, so this is already problem of migrating if it is a big project.
Using Angular is like you have a full equipment ARMY, You can fight and win, actually I want to say with Angular you have all the tools you need to do what ever you want to do in the same place. It's like a full kitchen with everything you need to cook your food. Angular is my love
Im feeling like Flutter and react are way more dynamic with beautiful UI and animations and everything in the same page no need scss, css, Bootstrap not even html etc react and flutter is all in one class, all in one single page and no need to create folders components with 4 or 5 ts, html, css and routing, modules, export, declaration and all that is not easy to understand
@@putinninovacuna8976 well it's half truth. Angular is way more organised, and when u switch project you will not be in shock because of fancy new libraries and the project structure. If u like one page one component, u can very well do that in Angular too. React is really good when u want some quick MVP do be done. Its fast and lightweight. Both have their place.
yes, in React you have too choose between React context, Redux various ways and packages (formik or react-hook-form ) to handle forms, react-fetching-library vs. axiosa or even React.js vs React+TypeScript etc. in Angular it is more simple and .js in outdated now
Having written about a dozen+ react tutorials, I've just realized this morning it's better for new beginners to learn Angular first because it teaches you structure and good programming habits. With React, you have to spend a lot of time researching the best way of organizing your project structure.
Rather than 'Angular does stuff for you so you don't have to think for yourself', I see it as it forcing you to use the best practices. Angular is an excellent foundation and learning tool for how you should structure and future proof a scalable project.
I've done quite a lot of work on both, I actually am working now in a government project completely done in react and I can see it's benefits, but I also work in angular in other large scale projects and hands down I choose angular, If I'm hired to do react work I'd go for it, but if I have to choose for my own system, angular.
I worked with React for the last 3 years It was very good, now In my current job we use angular and it's a joy, maybe I liked it more than react, opinionated stuff is good when you switch projects often because even when you're new in the team you adapt fast.
I agree. I have used both. React 'always' has problems, thus, noobs use it, and they hire someone to fix it up, and it 'always' has issues. Angular is much better. It doesn't attempt weird javascript wrappers like 'usestate' which can simply break. Everything is clear. You can do anything, and anything else, use Javascript. In React, it's always a 'big problem'. People are hyped about react because they think Facebook made it and has special performance from it, but it's a noob's language, it 'can' be used correctly, but imo Angular is way better.
I have been learning Angular and have used it in some of the projects which I thoroughly liked and enjoyed but I wanted to checkout why React was getting all the hype especially in YT so I started seeing some of the tutorials but React feels like an unfurnished house which costs less and is ready to be customised on the other hand Angular feels like a fully furnished luxurious house (costs more!!) Conclusion: I am not able to learn react cause Angular ruined every upcoming framework for me I just love it
Just learn both, I also learn and love Angular first, but you gotta keep up with the trend. React has it's uses, and in the end all frameworks look the same when you have work with a lot of them.
@@javier.alvarez764 Hello, Can I learn angular and then react later? Is it ok to learn two frameworks? coz I want to focus one only one and master it instead of confusing myself with both of them.
Angular is great for devs with a traditional CS background in my opinion. Object oriented approach and having a type system are some of the features that could make Java and C# developers feel more at home than writing JSX in React or Vue. React and Vue have a more modern approach but to be honest I really think that it comes down to your personal preference. Do you like templates? Go with Vue. Do you like JSX and pure JS? Go with React. People can get very tribal when it comes to this stuff but at the end of the day it doesn't matter what tools you use as long as your end product is solid.
You say "modern approach" but what really does that mean? It's not 'leaner' in any way, the 'bytes sent' doesn't become less, it doesn't 'load any faster'. You willbe stuck doing something you could already do, if it's vue/react with their weird javascript wrappers (all of them compile back to Javascript anyway) and stuck wondering why it isn't working with 0 support given. They have more jobs because of this because noobs use React/Vue tools and then get stuck, and even experts will struggle using the tools for longer once called to work on it. They are trying to for some reason format Javascript into .ts files even with weird things like putting
characters and javascript in the .ts files sometimes. It's totally ass backwards. You might as well do raw Javascript instead of React then, if you already know, raw javascript basically is doing what jsx is doing. Angular is the only one that has become beneficial to simply use even if you're still new and don't optimize code. It offers nice things you can just add directly to the html, as well as benefits where even most people not understanding it would benefit from it. You already stated some benefits as well. JSX isn't even faster or beneficial, it's just like changing a format, then the weird usually 'broken' things like usestate, are wrappers for javascript using like the local/session data in the end, so it's all basically crap that usually reformats but runs on javascript, except for Angular or something that 'actually works well'. The fact you have to learn how to use something and know underlying what it already does is pathetic and wastes time for react/vue aside from any time a basic thing 'fails to run', you will be stuck for longer. Angular is a nice example where raw javascript can even be used interchangably, good file structure, and improves things rather than adds problems, even for smaller projects.
+ Angular We have C# developers. So Typescript and strict framework was our choice. They learn fast. Typescript and C# are developed and maintained by the same company - Microsoft. I think its more about JS vs TS than React vs Angular. It is more about there you came from: front-end or back-end. Same story with NodeJS. Its for front-end developers. And it is more profitable to choose not - where more vacancies, but - where fewer specialists :)
working with react for the past 2 years and it's true, developer (beginner) can easily learn about the concept i.e. props and state, jsx, lifecycle...compare to Angular which I've learnt for the past two months, it is structured and neat however it's very challenging to understand the concept...and it's true, i always refer to the docs because its hard to memorise Angular stuff!
I was taught REACT out the gate, but a lot of interviewers have asked about ANGULAR compared to VUE, so my next endeavor is angular. Thank you for the video!
yes, in React you have too choose between React context, Redux various ways and packages (formik or react-hook-form ) to handle forms, react-fetching-library vs. axiosa or even React.js vs React+TypeScript etc. in Angular it is more simple and .js in outdated now
At my previous job, we used React with Typescript, and I loved it. TS makes React a lot more organized and less difficult to maintain. Should be the default in my opinion.
I'm personally very much enjoying my last half year with Angular (Started with 10). Particularly since I absolutely love having recognizeable structure. In the end, it's all about cognitive load required when you go into a project blind until you can get behind what's happening and work. Angular does that for you. Yeah you have a harsh learning curve, but guess what? A lot of the things it forces you to learn are things that are pretty beneficial to learn in general. The concept of services, typescript, properly internalizing rxjs concepts, DI and more. It's all just good things to know either way, so may as well learn them from the start. Add on top of that, that you only rarely need to include external libraries and you've got something that may be harder to get going, but is going to not make you want to abandon a project half a year from now.
I had to use Angular for a senior portfolio project last year in college and I didn't like it at first. However, I recently started learning Angular again since I really want to learn Ionic for mobile application development and I gotta say, I think I was a bit harsh on Angular initially. There are so many great modules that React does lack and I believe React is a bit harder to learn because of the amount of concepts you need to be able to grasp. By the way, I really like Vue too for similar reasons.
When I worked turner broadcasting we had teams using both angular 2+ and react. I would frequently hear the react guys curse in anger while coding while the angular devs would just happily write code. I also noticed the react guys had a rough time moving to other react projects and getting productive. The angular guys had a much easier time working on other angular projects. I think that was because all of the angular projects had the same code structure since angular is more of a complete framework. Another thing I would mention is angular 11 min project size and render performance is very competitive today. A react app grows pretty quickly once you start adding in things that come with angular.
Wow very interesting to read this. Especially from company’s as big as Turner broadcasting. I work for a big company and I prefer angular and the rest of the business prefer react. But I can crank out the projects so much faster than they can
@@CodingAbroad it puzzles me to this day why so many pro devs like using react to develop medium to large apps using react. From what I have seen these kind of apps built with react reach the same bundle size as those built with angular. There is no savings in app size, which is one of the biggest arguments I here for using react.
@@donmorris4506 I think because react came out first they have to appear loyal to it. I know all 3: Vue, React and Angular but the single thing that wins the argument is complex form validation. It’s a breeze in Angular’s reactive forms. But I had real problems in Vue and React, when you need to change a particular fields validation rules AFTER run time
I have only dabbled in React, and have used Angular in production. That said, I find learning Angular first to be more universal. If you know Angular you can pick up React quickly. If you know React, I am not sure the reverse is as true.
Tech recruiter here with both react+angular background. I can confirm, react community is filled with noobs and "bootcamp developers" and "kickstart your blabla" udemy courses. The complexity of angular filters out the bad developers from the good ones. Thank god my project manager switched to angular. Our react days were hell, more than 50% turnover rate - we hire people and fire them in less than six months because the senior devs were not satisfied with their performance on code reviews. *Post an angular job - 50+ applicants, 90% strong candidates, a few bad ones who are new to webdev but already have strong c++/c# background(so its easy to teach them). *Post a react job - 300+ applicants, newbies, bootcamp resumes, shtty code samples, hobbyist, obviously googled "frontend interview questions". out of 20 resumes only 1 strong candidate. good luck filtering the pack of sheep.
Thank you! Being on the track of becoming a self-taught coder (partly via udemy) I'm quite interested in the main issue/gripe you see with udemy-taught applicants. Is it mainly the code quality and speed that's lacking? Thus would you suggest more practice? Something else?
This is an issue with the lack of programming knowledge/ bad recruitment process, NOT an issue of the react framework. A "noob"/ "fresh bootcamper" can never know as much as a senior, so the expectations should not be the same. Seniors should teach "noobs" and if this is not possible then don't hire "noobs" in the first place.
@@mstam853 if you can read as much as you can comment you would know that NOBODY said this is an issue with the react itself(which is a library btw not a framework). i specifically pointed out its an issue with the react community. newbies will choose react. hobbyist will choose react. and in some cases, even aspiring angular devs who realize they are not good enough to learn angular will eventually go run and choose react. the community is filled with noobs. that is a fact. And no, its not a problem with my recruitment process and team. Because if it is - then we would be having the same problem whether its angular or react. The senior devs have no complaints against my angular recruits, no problems with my django recruits and no problems with my ux designer recruits. So im pretty damn sure i did a pretty darn good job in the recruitment process. Angular has a better good vs bad developer ratio. that is a fact and thats not my fault.
@@ninjedi6710 really no need to get offensive here ;) First you called developers 'pack of sheep' and then you questioned my reading abilities. But I will let that speak for itself. I just found it unfair to disregard the whole react community because of the dificulties you've encountered filtering out good candidates. Every community has noobs and pros, it's only natural. I don't know how the good vs bad developer ratio is, so I cannot comment anything on that. It does seem that due to the react adoption among bootcamps, a lot of aspiring devs are learning it, so this may well be true, BUT I would not go as far as to say "it's a fact" - at the end of the day it's still just your personal experience as one tech recruiter. All the best to you mate!
Hey James this was a good video, I'm a lead at American Airlines now days React has falling in popular in big enterprise organizations because most be companies prefer frameworks over libraries. Most startups use react because it's easy and fast and good for new devs. Only issue I had with using React is that it relies too much on 3rd party libraries in which big companies are against. React is really only good for monolithic app. I prefer Angular Vue for big apps
I hated Angular before, after i worked with angular for couple of months and then learnt nestjs, i never feel i should go back to any other frameworks / libraries.
Thanks for the video. I just started angular and I love it. It's so structured and compact. I also like React maybe in the near future I might learn React.
@@IamHamzaGujjar It depends on where and what you work on. There are enough companies that use Angular or completely different things. If you want to learn a framework but don't know which one, it doesn't matter. You can adapt what you've learned super quickly. So don't worry about which framework you want to learn. I think Vue.js is quite nice, especially because Tailwind.css fits well with it. But as I said, it doesn't really matter.
Any typical web applications will require many 3rd party libraries if you are using React and will become very messy if you are not disciplined in your structure or architecture. Eventually you will be bringing another framework like Next or Gatsby which require more 3rd party libraries..and everytime you reinstall the project, you get lots of vulnerability warnings where you just have to wait for the library owner to update....so I would rather depend on Angular for the structure and built-in features.
Angular = Microsoft Technologies (Typescript, Reactive Extensions RxJs) and Google Software Engineering (DI, TDD, ...) - Angular is for Enterprise! React = just Javascript with some synctactic sugar on it. Typescript will come to React like it does in all major frameworks.- React is for Individual Devs!
During my career of 16 years as a software engineer, I've worked with Java, JSP, Struts, Spring framework, a bit with C/C#/Python, PHP & Zend framework, jQuery, AngularJs & Angular, and a very little bit with React, and honestly with AngularJs and now with Angular I have the best Developer Experience. I tend to agree with "Jasar Wadlow", as he said: - React: When you buy a car, you only get the chassis and engine. BYO brakes, exterior, and interior, wheels, etc. - Angular: When you buy a car, you get the car, the car dealership, the engineers.
It’s kind of ironic... Angular definitely has a steeper learning curve, but if you’re not acquainted with software architecture and design principles, it kind of takes care of that for you, and therefore, can be perfect for beginners. I like them both but will say I learned a lot about architecting software by using Angular as my first and primary framework
I take a different perspective on that. If you aren’t used to those concepts angular is easy to feel intimidating with all that’s going on lol interesting how different people have different perspectives
As self taught new to coding developer I decided to learn angular because what it provides out of the box I don’t mind learning curve as I got all I need in one place
Same here! I found react to be very confusing while Angular is more structured. I started a big big project for a client 2 weeks ago and although I have much more experience in React, I chose Angular because of the reason you mentioned.
Native mobile app developer here. I been learning React for one main reason. React Native. I get bombarded with request as with React Native as I develop native iOS apps using Swift and native Android using Kotlin. They market is desperately looking for native mobile developers that know React Native.
When I started working with Angular, Never touched React. React is like Express, Do everything yourself mostly. Angular is like Nestjs (Not really, Nestjs is like Angular) You get everything you ever wanted Edit: I still prefer React and Express
Best comparison video I've ever seen ! Non biased which is really hard to find these days. I've started to work with a big enterprise and they prefer Angular like you say. Although I'm interested in using new frameworks like Svelte for my personal projects I can understand why they prefer it. Although at first glance Angular looks harder than React and Svelte even looks easier than React.
I also had this question on my mind last year, and happy that we have come to the same conclusion. I've been studying React for a while now and has been loving it.
I have worked for 8 years in angular and only 2 years on React . I felt React is far better than Angular in the sense you are using javascript all the way and you are not too much concerned with OOP concepts which I have no problem but it is not needed if you just want to build a good web application, with Reactjs you can use functions to solve all the problems.
I learned react tutorial and then got a job for Angular which i learned on Job , yes React is promising, but Angular is more powerfull. Just personal opinion, clearly I could be wrong.
In bigger projects, Angular definitely has a huge plus over React, that it guarantees the project would remain structured in the same style, versus in React, there is no guarantee there shouldn’t be ten different styles in the code base
I like Angular for newer developers learning a framework. As an example you can just lookup how to do routing in angular and there is documentation and there is one way to do it. With React you can pick a router but for a new developer just wanting to create routes, now they have a decision to make - one they probably aren’t equipped to make. Things like Next definitely help with this. At this point I wouldn’t suggest learning “React” as much as I would suggest learning Next.
Great comparison! My opinion is that you should use Typescript in both Angular and React in a professional project. In Angular i think that rxjs is very interesting and is motivating me to be more clever. In React I learn more about javascript and functional programing aswell as beeing closer to the html. Choose React if you want to learn js, html, css. Choose Angular if you don't have time time learn, but want to make the best descisions.
I’ve just changed my job. There are SO many companies using Angular: NEC Software, Virgin Media and MetroBank just to mention a few. There are also very different industries using Angular, my new job is with a biotech / medical company
I used vue in the beguinning, i tried react once or twice, and i've working with angular over the last years, and i think the major problem is angular is much bigger and requires much more knowledge than react, that's why most of young devs prefer react instead of angular. Whe you are young and look at the angular code it's scary, but react theres no many code just a few lines, it's more easy to start with. i think in the end both are good and does the job. It allways depend on code quality of the developer. Most of people look at frameworks and languages like football teams. They are just tools.
@@toddzmijewski6002 The problem is not to be easy or hard, actually angular is very easy, all the frameworks are easy, that's why is a framework to be accessible to all devs. Developers need to understand when to use one or another framework. Easy or hard depends on your skills. If someone wrote bad code, the framework does not solve the quality of the code, frameworks are just guidelines.
@@PauloSantos-yu1tn I think a good framework or platform does facilitate quality code. For example, teaching people to think in terms of isolated components, services results in smaller, decoupled classes. Making things like dependency injection an integral part of the framework facilities the concept and importance of loose coupling. Frameworks that strictly enforce MVVM will teach someone how to separate view and business logic. Great frameworks, platforms force you to use use well recognized patterns whether you recognize them or not.
@@toddzmijewski6002 Agree totally, i personally use them and one of them is angular, but if i advice someone to learn something i would probably say to learn data structures and algorithms and real low level functionalities. When you are developing for smaller project that's ok, but when it scales up too much you need to speed up things and that speed does not come from frameworks. Frameworks don't do everything, they provide you a structure which is more than good to start something. Once more, depends on what you are doing. Frameworks are just tools, if they where used incorrectly could be bad.
I can't agree more with you in the content of your video. Personally I have suffered the 3 (angular, react and vue) and loved only 2 of them, but mostly I agree with everything you have said. One thing that makes me regress to not like angular is into granular concepts that can be solved in react way simpler (and in vue[ish]), like refs, render props, contexts. I think those concepts, as a comparison create unnecessary fatigue for angular devs. Another downside of angular (in my personal experience) is the path from angular 2 to angular 4 was really painful to adopt it. Luckily that will become history for new devs, but it was such a pain to get things right with guides to migrate from angularJS to angular2. I honestly thought for years that migration from angularJS to react was way simpler in many ways. But decisions are not always at the reach of developers and experiences like mine are hard to be told.
Oh and one thing that pisses me off is that people tend to like angular, because what they really like is RXjs and Typescript. Junior devs tend to confuse that what is cool is not really angular, and that you can get RxJS and Typescript beauty outside angular.
@@juancarlosperezchavez7698 I also see this with Angular folks. Do they really need RxJS for every project? I thought it was for representing a continuous flow/stream of data, which I don't think every project needs and thus those Angular folks are probably cluttering the codebase with more complexity than is necessary... Don't get me wrong, I like the idea of Observables, but I'm not going to use them if it doesn't make sense.
Just learn React Typescript. You learn everything about react and you can do angular too if the jobs need. If you are good at typescript, you just need 1 or 2 weeks and you can start coding angular just fine
I love both. I started with Angular. But i have the feeling that React is more popular. It has a big community and its every where on the web. You find more content in react than angular in youtube or other platforms.
I think I might try angular. Was very disappointed with how “empty” React feels. It’s easy to use but damn, You need to install a lot of packages to get the bare minimum. Nextjs helps and it certainly has made my react experience easier but I would much rather have a single framework that has everything I need.
5 years working with Angular most of that component based from 2 through 10 or 11 (I lose track). I did some React and never liked it from the start. Forced me to deal with state management, prevent rendering before I wanted to, kept deprecating built in functions. On mount, On update. On Donner. On Blitzen. Then there are reducers. Then along comes React Hooks and lets redo the whole damn mess. So I guess you know which I prefer. I recently decided not to pursue jobs that mentioned React. For me if React is the only web UI option in the future I will just stay on the back end.
@@CodingAbroad We rewrote our backend on node using TS and MVC principles. Switching to Angular would allow us to reuse a lot of components between FE and BE. For example User class is the same on FE and BE. Also our new teamled has a lot of experience with Angular and nobody on the team has the same level of knowledge on Angular.
If you're new to both of these, just go with React. Not because it is better than Angular. Just because and only because it is more popular right now. Other than that if you're a good developer you don't have any issues with both.
Dont know about react but there are not many good UI Toolkits for Angular. Material is probably the best in terms of consistency and quality, but the development is ultra slow and not so much community contributions (in fact, alot of community stuff gets rejected being merged into the official repo). So you have like 1 new feature/year in material :P ... I feel like in Angular simple things are sometimes taking alot of time to implement. Especialy if you have many dialogs, its repetitive boilerplate over and over again. If you use Angular and you feel the need of using proper state-mangement your choices are NgRX, NgXS, Akita and MobX. My favorite is Akita (encapsulates Redux in Service classes) as it reduces the boilerplate code to a minimum, I think its almost equivalent to NgRx-Data
@@JamesQQuick React because of Hooks , I really enjoy being able to write functional components which have state without having to worry about things like the 'this' keyword at times. :) Sorry for the delay in response, I didn't see your comment.
Very interesting. I have chosen React as the first technology to learn for me. I really love it and combined with Typescript it is also really powerfull. Sure, you have to install some packages but this is 1 line of CLI code and there you have it. Everything is awesomely well documented. But I will definetely give Angular a try one day.
I know very well React but I can't find a job in it(I already work somewhere as a developer). For some reason in my country the job offers in Angular are way more than in React. Also most companies that use React are amateurs from my experience. And this is a shame because I really like React, but it seems that I will have to learn Angular...
Wondering why you did not speak about Vue. Is it because the creator was once a Google Employee and had worked on Angular? I personally learnt React first then learnt Angular for another project. Somehow I found the structure Angular gave me more comfortable. It felt harder to set up but easier to use and debug.
I love java and i feel way to uncomfortable doing react, that also because i suck at it, i tried angular but at that time i didn't know reactive programming either how DI worked, i'd ended up jumping to angular
I've always used react and a lot of things was bothering me with it, so i tryied Angular and never came back to react. Never tryied with vue, but currently i am learning flutter so i don't have much time for it.
6:15 A React-based framework gives you what Angular doesn't in terms of structure and opinion? Sorry mate but you really need to explain that because that's highly debatable and honestly I find it hard to believe. For example, something like Next.js over React isn't that much different from Angular with perhaps Angular Universal enabled for SSR.
I would say that’s a pretty common opinion. Angular has built in routing, file structure, services, etc. react doesn’t really have that built in. You have to reach for a third party package for routing. It doesn’t give you any specific options about file structure. Regardless, if you feel different that’s great too
Also not sure what nuxt.js has to do with React? Maybe you’re talking about next.js? If so, that’s a framework built on top of react. That’s a different comparison than react vs angular
Thanks for the explanation. I'm doing a professional change in my career and I'm working to get a place in web development, so I appreciate your clear recommendation.
Can you create a nice and beautiful UI with Angular, just like you can with React? Basically the question is: can I create the same app clone, like Amazon with either angular or react?
what about react with typescript and tsx? I had that experience and quite useful although I found it somewhat intimidating to find the suitable and appropriate library and module especial with react native
Great Video. I agree with you 100% in all that you said. I do think there may be a little bit of a learning curve in terms of expectations of what react is. However, Facebook has a way of producing technologies that have a more natural feel for existing workflows. I totally agree that Angular is built for enterprise software. That may have been their goal. It is however quite bloated. Nevertheless, I agree both are worth being conversant with along with VueJS if you can accommodate that.
Vue: When you buy a car, you get a car.
React: When you buy a car, you only get the chassis and engine. BYO brakes, exterior and interior, wheels, etc.
Angular: When you buy a car, you get the car, the car dealership, the engineers, the salespeople, the technicians, and a complimentary petrol station. Buyer assumes all risks and operating costs.
lol nice analogy
Angular is like Visual Studio IDE - a billion icons and panes. Comparatively React is like VS Code - lightweight and you add just what you want (hence its popularity) lol
Vue - wheels possibly just the exhaust or seats
React - wheels possibly just the exhaust or seats
Angular - the entire, complete car - learn to drive it and only need one.
@Gus Erland Angular is designed for large project, giving your consistency and standardization so that you do not lose maintainability over time. the 3 major web frameworks all exists for a reason
@Gus Erland what you mentioned could be a reason but not all .. give you an example, for angular, there is one official way to do http request from very beginning. but in react, before it is official httpclient, you have a lot https client libraries, so this is already problem of migrating if it is a big project.
As a developer apprentice, I learned to code with React. Then come my internship and I worked with Angular. Never touched React again...
@@gradientO After my internship, a big tech company offer me a full time job and the stack is Angular / Java
@@gradientO I am mainly a frontend developer but for the project we work on, my manager make sure I'm fullstack
I am on the same stage now, about to start learning angular for my internship.
was it easy to make the transition from react to angular?
@@danneytee Nothing is easy, especially in programming :) Angular is more complex, because React is a library, not a framework
Using Angular is like you have a full equipment ARMY, You can fight and win, actually I want to say with Angular you have all the tools you need to do what ever you want to do in the same place. It's like a full kitchen with everything you need to cook your food. Angular is my love
Same
Cock your food...🤨😳
Im feeling like Flutter and react are way more dynamic with beautiful UI and animations and everything in the same page no need scss, css, Bootstrap not even html etc react and flutter is all in one class, all in one single page and no need to create folders components with 4 or 5 ts, html, css and routing, modules, export, declaration and all that is not easy to understand
@@putinninovacuna8976 well it's half truth. Angular is way more organised, and when u switch project you will not be in shock because of fancy new libraries and the project structure. If u like one page one component, u can very well do that in Angular too. React is really good when u want some quick MVP do be done. Its fast and lightweight. Both have their place.
yes, in React you have too choose between React context, Redux various ways and packages (formik or react-hook-form ) to handle forms, react-fetching-library vs. axiosa or even React.js vs React+TypeScript etc. in Angular it is more simple and .js in outdated now
Having written about a dozen+ react tutorials, I've just realized this morning it's better for new beginners to learn Angular first because it teaches you structure and good programming habits. With React, you have to spend a lot of time researching the best way of organizing your project structure.
Rather than 'Angular does stuff for you so you don't have to think for yourself', I see it as it forcing you to use the best practices. Angular is an excellent foundation and learning tool for how you should structure and future proof a scalable project.
I've done quite a lot of work on both, I actually am working now in a government project completely done in react and I can see it's benefits, but I also work in angular in other large scale projects and hands down I choose angular, If I'm hired to do react work I'd go for it, but if I have to choose for my own system, angular.
I worked with React for the last 3 years It was very good, now In my current job we use angular and it's a joy, maybe I liked it more than react, opinionated stuff is good when you switch projects often because even when you're new in the team you adapt fast.
I do appreciate opinionated frameworks to take some of the thinking out of it lol
I agree. I have used both. React 'always' has problems, thus, noobs use it, and they hire someone to fix it up, and it 'always' has issues. Angular is much better. It doesn't attempt weird javascript wrappers like 'usestate' which can simply break. Everything is clear. You can do anything, and anything else, use Javascript. In React, it's always a 'big problem'. People are hyped about react because they think Facebook made it and has special performance from it, but it's a noob's language, it 'can' be used correctly, but imo Angular is way better.
Angular 11 was amazing. I love angular especially for the code structure
Yuyliiuuip it up
I have been learning Angular and have used it in some of the projects which I thoroughly liked and enjoyed but I wanted to checkout why React was getting all the hype especially in YT so I started seeing some of the tutorials but React feels like an unfurnished house which costs less and is ready to be customised on the other hand Angular feels like a fully furnished luxurious house (costs more!!)
Conclusion: I am not able to learn react cause Angular ruined every upcoming framework for me I just love it
Just learn both, I also learn and love Angular first, but you gotta keep up with the trend. React has it's uses, and in the end all frameworks look the same when you have work with a lot of them.
@@javier.alvarez764 Hello, Can I learn angular and then react later? Is it ok to learn two frameworks? coz I want to focus one only one and master it instead of confusing myself with both of them.
@@coding_for_life6853 Get decent at one, then start learning the other. It won't take 100 years
Angular CLI is just the love of my life. Easy to scaffold anything you want.
Angular is great for devs with a traditional CS background in my opinion. Object oriented approach and having a type system are some of the features that could make Java and C# developers feel more at home than writing JSX in React or Vue. React and Vue have a more modern approach but to be honest I really think that it comes down to your personal preference. Do you like templates? Go with Vue. Do you like JSX and pure JS? Go with React. People can get very tribal when it comes to this stuff but at the end of the day it doesn't matter what tools you use as long as your end product is solid.
Agree with all of this!
You can also use typescript with React...
You make angular sound old and boring.
You say "modern approach" but what really does that mean? It's not 'leaner' in any way, the 'bytes sent' doesn't become less, it doesn't 'load any faster'. You willbe stuck doing something you could already do, if it's vue/react with their weird javascript wrappers (all of them compile back to Javascript anyway) and stuck wondering why it isn't working with 0 support given. They have more jobs because of this because noobs use React/Vue tools and then get stuck, and even experts will struggle using the tools for longer once called to work on it. They are trying to for some reason format Javascript into .ts files even with weird things like putting
characters and javascript in the .ts files sometimes. It's totally ass backwards. You might as well do raw Javascript instead of React then, if you already know, raw javascript basically is doing what jsx is doing. Angular is the only one that has become beneficial to simply use even if you're still new and don't optimize code. It offers nice things you can just add directly to the html, as well as benefits where even most people not understanding it would benefit from it. You already stated some benefits as well. JSX isn't even faster or beneficial, it's just like changing a format, then the weird usually 'broken' things like usestate, are wrappers for javascript using like the local/session data in the end, so it's all basically crap that usually reformats but runs on javascript, except for Angular or something that 'actually works well'. The fact you have to learn how to use something and know underlying what it already does is pathetic and wastes time for react/vue aside from any time a basic thing 'fails to run', you will be stuck for longer. Angular is a nice example where raw javascript can even be used interchangably, good file structure, and improves things rather than adds problems, even for smaller projects.
+ Angular
We have C# developers. So Typescript and strict framework was our choice. They learn fast.
Typescript and C# are developed and maintained by the same company - Microsoft.
I think its more about JS vs TS than React vs Angular.
It is more about there you came from: front-end or back-end.
Same story with NodeJS. Its for front-end developers.
And it is more profitable to choose not - where more vacancies, but - where fewer specialists :)
working with react for the past 2 years and it's true, developer (beginner) can easily learn about the concept i.e. props and state, jsx, lifecycle...compare to Angular which I've learnt for the past two months, it is structured and neat however it's very challenging to understand the concept...and it's true, i always refer to the docs because its hard to memorise Angular stuff!
I was taught REACT out the gate, but a lot of interviewers have asked about ANGULAR compared to VUE, so my next endeavor is angular. Thank you for the video!
when i work in angular project i miss react, when i work with react project i miss angular, there is just no escape
I can feel that :D Maybe we should just go back to plain JS or use c++ with webassembly :D
She is cute as hell
When I debug with react i miss my life.
are you really that cute?)
yes, in React you have too choose between React context, Redux various ways and packages (formik or react-hook-form ) to handle forms, react-fetching-library vs. axiosa or even React.js vs React+TypeScript etc. in Angular it is more simple and .js in outdated now
At my previous job, we used React with Typescript, and I loved it. TS makes React a lot more organized and less difficult to maintain. Should be the default in my opinion.
Yeah, maybe they don't use it because Facebook has flow js to make js strong typed
I'm personally very much enjoying my last half year with Angular (Started with 10).
Particularly since I absolutely love having recognizeable structure. In the end, it's all about cognitive load required when you go into a project blind until you can get behind what's happening and work. Angular does that for you. Yeah you have a harsh learning curve, but guess what? A lot of the things it forces you to learn are things that are pretty beneficial to learn in general. The concept of services, typescript, properly internalizing rxjs concepts, DI and more. It's all just good things to know either way, so may as well learn them from the start. Add on top of that, that you only rarely need to include external libraries and you've got something that may be harder to get going, but is going to not make you want to abandon a project half a year from now.
I had to use Angular for a senior portfolio project last year in college and I didn't like it at first. However, I recently started learning Angular again since I really want to learn Ionic for mobile application development and I gotta say, I think I was a bit harsh on Angular initially. There are so many great modules that React does lack and I believe React is a bit harder to learn because of the amount of concepts you need to be able to grasp. By the way, I really like Vue too for similar reasons.
When I worked turner broadcasting we had teams using both angular 2+ and react. I would frequently hear the react guys curse in anger while coding while the angular devs would just happily write code. I also noticed the react guys had a rough time moving to other react projects and getting productive. The angular guys had a much easier time working on other angular projects. I think that was because all of the angular projects had the same code structure since angular is more of a complete framework.
Another thing I would mention is angular 11 min project size and render performance is very competitive today. A react app grows pretty quickly once you start adding in things that come with angular.
Wow very interesting to read this. Especially from company’s as big as Turner broadcasting. I work for a big company and I prefer angular and the rest of the business prefer react. But I can crank out the projects so much faster than they can
@@CodingAbroad it puzzles me to this day why so many pro devs like using react to develop medium to large apps using react. From what I have seen these kind of apps built with react reach the same bundle size as those built with angular. There is no savings in app size, which is one of the biggest arguments I here for using react.
@@donmorris4506 I think because react came out first they have to appear loyal to it. I know all 3: Vue, React and Angular but the single thing that wins the argument is complex form validation. It’s a breeze in Angular’s reactive forms. But I had real problems in Vue and React, when you need to change a particular fields validation rules AFTER run time
I have only dabbled in React, and have used Angular in production. That said, I find learning Angular first to be more universal. If you know Angular you can pick up React quickly. If you know React, I am not sure the reverse is as true.
Tech recruiter here with both react+angular background. I can confirm, react community is filled with noobs and "bootcamp developers" and "kickstart your blabla" udemy courses. The complexity of angular filters out the bad developers from the good ones. Thank god my project manager switched to angular. Our react days were hell, more than 50% turnover rate - we hire people and fire them in less than six months because the senior devs were not satisfied with their performance on code reviews.
*Post an angular job - 50+ applicants, 90% strong candidates, a few bad ones who are new to webdev but already have strong c++/c# background(so its easy to teach them).
*Post a react job - 300+ applicants, newbies, bootcamp resumes, shtty code samples, hobbyist, obviously googled "frontend interview questions". out of 20 resumes only 1 strong candidate. good luck filtering the pack of sheep.
Thank you! Being on the track of becoming a self-taught coder (partly via udemy) I'm quite interested in the main issue/gripe you see with udemy-taught applicants. Is it mainly the code quality and speed that's lacking? Thus would you suggest more practice? Something else?
This is an issue with the lack of programming knowledge/ bad recruitment process, NOT an issue of the react framework. A "noob"/ "fresh bootcamper" can never know as much as a senior, so the expectations should not be the same. Seniors should teach "noobs" and if this is not possible then don't hire "noobs" in the first place.
@@mstam853 if you can read as much as you can comment you would know that NOBODY said this is an issue with the react itself(which is a library btw not a framework). i specifically pointed out its an issue with the react community.
newbies will choose react. hobbyist will choose react. and in some cases, even aspiring angular devs who realize they are not good enough to learn angular will eventually go run and choose react. the community is filled with noobs. that is a fact.
And no, its not a problem with my recruitment process and team. Because if it is - then we would be having the same problem whether its angular or react. The senior devs have no complaints against my angular recruits, no problems with my django recruits and no problems with my ux designer recruits. So im pretty damn sure i did a pretty darn good job in the recruitment process.
Angular has a better good vs bad developer ratio. that is a fact and thats not my fault.
@@ninjedi6710 really no need to get offensive here ;) First you called developers 'pack of sheep' and then you questioned my reading abilities. But I will let that speak for itself. I just found it unfair to disregard the whole react community because of the dificulties you've encountered filtering out good candidates. Every community has noobs and pros, it's only natural. I don't know how the good vs bad developer ratio is, so I cannot comment anything on that. It does seem that due to the react adoption among bootcamps, a lot of aspiring devs are learning it, so this may well be true, BUT I would not go as far as to say "it's a fact" - at the end of the day it's still just your personal experience as one tech recruiter. All the best to you mate!
when you read comments earlier you feel its all about angular... But this man made me feel good at end... Thanks
Hey James this was a good video, I'm a lead at American Airlines now days React has falling in popular in big enterprise organizations because most be companies prefer frameworks over libraries. Most startups use react because it's easy and fast and good for new devs. Only issue I had with using React is that it relies too much on 3rd party libraries in which big companies are against. React is really only good for monolithic app. I prefer Angular Vue for big apps
Has American Airlines switched to Angular from React?
I hated Angular before, after i worked with angular for couple of months and then learnt nestjs, i never feel i should go back to any other frameworks / libraries.
Thanks for the video. I just started angular and I love it. It's so structured and compact. I also like React maybe in the near future I might learn React.
About to learn React for my first job after university! Thanks for tips!
Angular was the first framework I learned. I find it super comfortable to code with, but I only use React/React Native now. The work must be done
Why did you switch to react?
@@IamHamzaGujjar Can't always choose at work and in my area there is more work for React.
@@No-no-no-no-nope is it true that most industries and organisations are now switching to React ?
@@IamHamzaGujjar It depends on where and what you work on. There are enough companies that use Angular or completely different things. If you want to learn a framework but don't know which one, it doesn't matter. You can adapt what you've learned super quickly. So don't worry about which framework you want to learn. I think Vue.js is quite nice, especially because Tailwind.css fits well with it. But as I said, it doesn't really matter.
@@No-no-no-no-nope Thanks man, its been a month now I’ve started to learn MEAN Stack..
Any typical web applications will require many 3rd party libraries if you are using React and will become very messy if you are not disciplined in your structure or architecture. Eventually you will be bringing another framework like Next or Gatsby which require more 3rd party libraries..and everytime you reinstall the project, you get lots of vulnerability warnings where you just have to wait for the library owner to update....so I would rather depend on Angular for the structure and built-in features.
Angular = Microsoft Technologies (Typescript, Reactive Extensions RxJs) and Google Software Engineering (DI, TDD, ...) - Angular is for Enterprise!
React = just Javascript with some synctactic sugar on it. Typescript will come to React like it does in all major frameworks.- React is for Individual Devs!
During my career of 16 years as a software engineer, I've worked with Java, JSP, Struts, Spring framework, a bit with C/C#/Python, PHP & Zend framework, jQuery, AngularJs & Angular, and a very little bit with React, and honestly with AngularJs and now with Angular I have the best Developer Experience.
I tend to agree with "Jasar Wadlow", as he said:
- React: When you buy a car, you only get the chassis and engine. BYO brakes, exterior, and interior, wheels, etc.
- Angular: When you buy a car, you get the car, the car dealership, the engineers.
It’s kind of ironic... Angular definitely has a steeper learning curve, but if you’re not acquainted with software architecture and design principles, it kind of takes care of that for you, and therefore, can be perfect for beginners. I like them both but will say I learned a lot about architecting software by using Angular as my first and primary framework
I take a different perspective on that. If you aren’t used to those concepts angular is easy to feel intimidating with all that’s going on lol interesting how different people have different perspectives
As self taught new to coding developer I decided to learn angular because what it provides out of the box I don’t mind learning curve as I got all I need in one place
I feel like both of you :)
Angular experience made me a better dev
Angular ♥️, Angular is very well structured, while I found react as a very well weird combination.
Haha I love the structure in angular!
Same here! I found react to be very confusing while Angular is more structured.
I started a big big project for a client 2 weeks ago and although I have much more experience in React, I chose Angular because of the reason you mentioned.
you can create Angular like structure in react. please look at Nx by nx.dev/
Native mobile app developer here. I been learning React for one main reason. React Native. I get bombarded with request as with React Native as I develop native iOS apps using Swift and native Android using Kotlin. They market is desperately looking for native mobile developers that know React Native.
When I started working with Angular, Never touched React.
React is like Express, Do everything yourself mostly.
Angular is like Nestjs (Not really, Nestjs is like Angular) You get everything you ever wanted
Edit: I still prefer React and Express
Best comparison video I've ever seen ! Non biased which is really hard to find these days. I've started to work with a big enterprise and they prefer Angular like you say. Although I'm interested in using new frameworks like Svelte for my personal projects I can understand why they prefer it. Although at first glance Angular looks harder than React and Svelte even looks easier than React.
If you’re familiar with angular or react already, svelte is definitely worth exploring
I also had this question on my mind last year, and happy that we have come to the same conclusion. I've been studying React for a while now and has been loving it.
I have worked for 8 years in angular and only 2 years on React . I felt React is far better than Angular in the sense you are using javascript all the way and you are not too much concerned with OOP concepts which I have no problem but it is not needed if you just want to build a good web application, with Reactjs you can use functions to solve all the problems.
Thank you! Such a wonderful comparison.
I learned react tutorial and then got a job for Angular which i learned on Job , yes React is promising, but Angular is more powerfull. Just personal opinion, clearly I could be wrong.
Same with me I learned react but got job on angular
Me as well
In bigger projects, Angular definitely has a huge plus over React, that it guarantees the project would remain structured in the same style, versus in React, there is no guarantee there shouldn’t be ten different styles in the code base
And so React is more flexible
@@harditsingh1381 which is a big disadvantage
I like Angular for newer developers learning a framework. As an example you can just lookup how to do routing in angular and there is documentation and there is one way to do it. With React you can pick a router but for a new developer just wanting to create routes, now they have a decision to make - one they probably aren’t equipped to make. Things like Next definitely help with this. At this point I wouldn’t suggest learning “React” as much as I would suggest learning Next.
Good job, James! I enjoy your video.
Glad to hear it!
Great comparison! My opinion is that you should use Typescript in both Angular and React in a professional project. In Angular i think that rxjs is very interesting and is motivating me to be more clever. In React I learn more about javascript and functional programing aswell as beeing closer to the html. Choose React if you want to learn js, html, css. Choose Angular if you don't have time time learn, but want to make the best descisions.
It's true when u said Angular is much more enterprise oriented so Angular it is :) .
I’ve just changed my job. There are SO many companies using Angular: NEC Software, Virgin Media and MetroBank just to mention a few. There are also very different industries using Angular, my new job is with a biotech / medical company
I used vue in the beguinning, i tried react once or twice, and i've working with angular over the last years, and i think the major problem is angular is much bigger and requires much more knowledge than react, that's why most of young devs prefer react instead of angular. Whe you are young and look at the angular code it's scary, but react theres no many code just a few lines, it's more easy to start with. i think in the end both are good and does the job. It allways depend on code quality of the developer. Most of people look at frameworks and languages like football teams. They are just tools.
Agree with all of this :)
I agree with you as well. What needs to be done to make Angular easier to understand and less scary?
@@toddzmijewski6002 The problem is not to be easy or hard, actually angular is very easy, all the frameworks are easy, that's why is a framework to be accessible to all devs. Developers need to understand when to use one or another framework. Easy or hard depends on your skills. If someone wrote bad code, the framework does not solve the quality of the code, frameworks are just guidelines.
@@PauloSantos-yu1tn I think a good framework or platform does facilitate quality code. For example, teaching people to think in terms of isolated components, services results in smaller, decoupled classes. Making things like dependency injection an integral part of the framework facilities the concept and importance of loose coupling. Frameworks that strictly enforce MVVM will teach someone how to separate view and business logic. Great frameworks, platforms force you to use use well recognized patterns whether you recognize them or not.
@@toddzmijewski6002 Agree totally, i personally use them and one of them is angular, but if i advice someone to learn something i would probably say to learn data structures and algorithms and real low level functionalities. When you are developing for smaller project that's ok, but when it scales up too much you need to speed up things and that speed does not come from frameworks. Frameworks don't do everything, they provide you a structure which is more than good to start something. Once more, depends on what you are doing. Frameworks are just tools, if they where used incorrectly could be bad.
I can't agree more with you in the content of your video. Personally I have suffered the 3 (angular, react and vue) and loved only 2 of them, but mostly I agree with everything you have said. One thing that makes me regress to not like angular is into granular concepts that can be solved in react way simpler (and in vue[ish]), like refs, render props, contexts. I think those concepts, as a comparison create unnecessary fatigue for angular devs. Another downside of angular (in my personal experience) is the path from angular 2 to angular 4 was really painful to adopt it. Luckily that will become history for new devs, but it was such a pain to get things right with guides to migrate from angularJS to angular2. I honestly thought for years that migration from angularJS to react was way simpler in many ways. But decisions are not always at the reach of developers and experiences like mine are hard to be told.
Oh and one thing that pisses me off is that people tend to like angular, because what they really like is RXjs and Typescript. Junior devs tend to confuse that what is cool is not really angular, and that you can get RxJS and Typescript beauty outside angular.
@@juancarlosperezchavez7698 I also see this with Angular folks. Do they really need RxJS for every project? I thought it was for representing a continuous flow/stream of data, which I don't think every project needs and thus those Angular folks are probably cluttering the codebase with more complexity than is necessary... Don't get me wrong, I like the idea of Observables, but I'm not going to use them if it doesn't make sense.
I am a vue fanboy and did tinker with angularjs yrs ago but I will definitely be learning react in 2021. I got hooked with react hooks 🤩
bro, Angular.js has been discontinued many years ago. Use Angular instead
Angular. Always, no question about it.
Hell Yes
How did u manage to learn angular??
Like I got stuck at downloading the starter pack, its so godamn heavy
🤣🤣
Just learn React Typescript. You learn everything about react and you can do angular too if the jobs need. If you are good at typescript, you just need 1 or 2 weeks and you can start coding angular just fine
I love both. I started with Angular. But i have the feeling that React is more popular. It has a big community and its every where on the web. You find more content in react than angular in youtube or other platforms.
I can feel u there. Even I like angular. On enterprise scale, noone can beat it. However for startups, react rules.
I think I might try angular. Was very disappointed with how “empty” React feels. It’s easy to use but damn, You need to install a lot of packages to get the bare minimum. Nextjs helps and it certainly has made my react experience easier but I would much rather have a single framework that has everything I need.
5 years working with Angular most of that component based from 2 through 10 or 11 (I lose track). I did some React and never liked it from the start. Forced me to deal with state management, prevent rendering before I wanted to, kept deprecating built in functions. On mount, On update. On Donner. On Blitzen. Then there are reducers. Then along comes React Hooks and lets redo the whole damn mess. So I guess you know which I prefer. I recently decided not to pursue jobs that mentioned React. For me if React is the only web UI option in the future I will just stay on the back end.
Watching this as my company decided to switch from react to angular
Wow that’s wild. What were their reasons?
@@CodingAbroad We rewrote our backend on node using TS and MVC principles. Switching to Angular would allow us to reuse a lot of components between FE and BE. For example User class is the same on FE and BE. Also our new teamled has a lot of experience with Angular and nobody on the team has the same level of knowledge on Angular.
both are great but i prefer angular for very big projects easier to maintain and easier framework in general
I'm using React for a long time, Angular is more structural
I have worked on Vue and React for the past 2years. Moving into Angular now, hope I will like it.
If you're new to both of these, just go with React. Not because it is better than Angular. Just because and only because it is more popular right now. Other than that if you're a good developer you don't have any issues with both.
Dont know about react but there are not many good UI Toolkits for Angular. Material is probably the best in terms of consistency and quality, but the development is ultra slow and not so much community contributions (in fact, alot of community stuff gets rejected being merged into the official repo). So you have like 1 new feature/year in material :P ... I feel like in Angular simple things are sometimes taking alot of time to implement. Especialy if you have many dialogs, its repetitive boilerplate over and over again.
If you use Angular and you feel the need of using proper state-mangement your choices are NgRX, NgXS, Akita and MobX. My favorite is Akita (encapsulates Redux in Service classes) as it reduces the boilerplate code to a minimum, I think its almost equivalent to NgRx-Data
Thanks James!
I love working with both!
Any preference?! Or both equally?
@@JamesQQuick React because of Hooks , I really enjoy being able to write functional components which have state without having to worry about things like the 'this' keyword at times. :) Sorry for the delay in response, I didn't see your comment.
Your ideas are intriguing to me, and I wish to subscribe to your newsletter
I appreciate your experience on your videos , to the point , very usefully, Thanks for sharing your experience
Do a little of both see what you like =] ; personally I am an Angular fan boy.
I use native js and knockout and love the combo. I believe knockout and Angular are 2 way bindings vs react is one way? This is a huge difference
3mins into the video. am so loving the analysis so far. I strongly recommend
Ah thanks so much!!
I'm very confused about which one should i start to learn, i've already finished typescript and with your video i think angular is the best choice
I think that’s a good bet!
@@JamesQQuick thank you ! i've already started angular and it's pretty awesome
@@iamdmonz from where you are learning?
Very interesting. I have chosen React as the first technology to learn for me. I really love it and combined with Typescript it is also really powerfull. Sure, you have to install some packages but this is 1 line of CLI code and there you have it. Everything is awesomely well documented. But I will definetely give Angular a try one day.
Angular 2 and 4 and some numbers all the way up-to 11* :)
Haha exactly!!
nice video, it was helpful, thanks
I need to build a small crud in front end what combo should I use, please someone help ?
Helped me a lot thanks💪
I know very well React but I can't find a job in it(I already work somewhere as a developer). For some reason in my country the job offers in Angular are way more than in React. Also most companies that use React are amateurs from my experience. And this is a shame because I really like React, but it seems that I will have to learn Angular...
If you don't mind me asking, what country is that?
@@ezekiel7467 Greece
Nice video James!
well in short learn both and decide for yourself , everything has pros & cons , you too have your strengths & weaknesses , play on your strengths
Wondering why you did not speak about Vue. Is it because the creator was once a Google Employee and had worked on Angular? I personally learnt React first then learnt Angular for another project. Somehow I found the structure Angular gave me more comfortable. It felt harder to set up but easier to use and debug.
I love java and i feel way to uncomfortable doing react, that also because i suck at it, i tried angular but at that time i didn't know reactive programming either how DI worked, i'd ended up jumping to angular
I'm learning React for the job opportunities. But eventually, I'll be sticking to Svelte once I get the ball rolling with freelance gigs.
That’s cool. I’ve touched svelte just a bit!
@@JamesQQuick one thing it has that I sorely want to have in React is scoped styling, in a nifty SFC.
What is sfc?
Oh, sorry--Single File Component.
Bye bye cluttered .module.scss files 😆
So helpful Thank you! Are there any updates you would add to this?
I am a control freak person, I choose Angular
I've always used react and a lot of things was bothering me with it, so i tryied Angular and never came back to react. Never tryied with vue, but currently i am learning flutter so i don't have much time for it.
6:15 A React-based framework gives you what Angular doesn't in terms of structure and opinion? Sorry mate but you really need to explain that because that's highly debatable and honestly I find it hard to believe. For example, something like Next.js over React isn't that much different from Angular with perhaps Angular Universal enabled for SSR.
I would say that’s a pretty common opinion. Angular has built in routing, file structure, services, etc. react doesn’t really have that built in. You have to reach for a third party package for routing. It doesn’t give you any specific options about file structure. Regardless, if you feel different that’s great too
Also not sure what nuxt.js has to do with React? Maybe you’re talking about next.js? If so, that’s a framework built on top of react. That’s a different comparison than react vs angular
@@JamesQQuick yes I meant Next.js. Sorry it's easy to get them mixed if you switch between them often.
@@PaulSebastianM Cool. Ya, I mix them up all the time! lol
very helpful, as I was confused with. thank you
How are the two from the performance and user exprience view?
Thanks for the explanation. I'm doing a professional change in my career and I'm working to get a place in web development, so I appreciate your clear recommendation.
both angular and react is good for 2021. but for short term 'hit and run' project, obviously react.
Angular is cool, but have ever heard about react with nextjs tho
Can you create a nice and beautiful UI with Angular, just like you can with React? Basically the question is: can I create the same app clone, like Amazon with either angular or react?
what about react with typescript and tsx?
I had that experience and quite useful
although I found it somewhat intimidating to find the suitable and appropriate library and module especial with react native
Whats the learning curve like going from react to angular?
You should learn both. I’ve learned angular and now learning react
Great, good job!
hate react love angular, wait until you have to do maintenance over a big react project and over a big angular project and you will see the difference
then why most of the websites are made with react not angular
@@amans6504 React is previous to angular, smaller learning curve, trends of the moment
Why everyone calling react framework, when it's not? It's library. Frameworks are angular and vue
Great Video. I agree with you 100% in all that you said. I do think there may be a little bit of a learning curve in terms of expectations of what react is. However, Facebook has a way of producing technologies that have a more natural feel for existing workflows. I totally agree that Angular is built for enterprise software. That may have been their goal. It is however quite bloated. Nevertheless, I agree both are worth being conversant with along with VueJS if you can accommodate that.
Thanks for this video, James!
You can use typescript with React too though right?
Yep you can. It’s just not the default
thank you for your inputs
Nice video. Good job. I like React/Next.js.