@digital-signage
any experience developer that understands both platforms will choose angular every time...
@rs2334
I started web development with VueJS and worked with it for around 6 months, then I moved on to another company that uses Angular 8 which I've been working at since (almost a year). I also did a few courses with React and React Native. There are things that both Vue and Angular have that for React you'd need a third party component: -v-if/*ngIf, v-for/*ngFor, v-model/[(ngModel)] and several other great things you can do on the HTML section but with React you'd need to mix up your JS/TS with your HTML which is super messy. --Routing. Angular to me is by far the best; it has everything you need for the most part that even Vue doesn't: -Modules which are useful for organizing big applications. -Sass/Scss auto processing. -Services which can be used like Redux/VueX but are much easier to use by just injecting them wherever you need them. -Observables which are useful. -Reactive forms which are incredible — probably my favorite feature of Angular. -Elvis operator. The only three things I miss from Vue compared to Angular are minor: -v-else equivalent. There is no *ngElse, you have to use *ngIf and reverse the condition which feels silly. -I like the HTML, script and styling being in the same file but still clearly separated (HTML top, script middle, styling bottom) because I just dislike having a lot of tabs open on my VS Code. -Quasar Framework. Angular has good component libraries like PrimeNG and Angular Material but Quasar is just incredible. I haven't tried Vue with TypeScript but I know it's possible; like you said TypeScript is just a must for all 3 at this point. React has React Native for mobile sure, but for a web dev that does mostly web-apps only like me its not an issue. I'd go with Angular every time.
@ninjedi6710
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++ 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.
@FidelSantana87
I totally agree about selecting Angular as the better choice for web apps, there are no doubts about the advantages of having a well-structured code since the beginning and also all the features that are included in the core, I like the angular way. There are plenty of third-party mature libraries that brings integration with trending technologies like GraphQL, NgRx, and many more. If you want to go through the JS stack, you can use Nest JS in the backend, which is the perfect match for Angular. But there are some disadvantages that we need to consider if we want to go with Angular. - It manipulates the real DOM, which is less efficient than using a virtual DOM (React and Vue does) - The propagation of events, it's a big issue when you have a lot of nested components, you can use the OnPush Change Detection strategy to avoid this, but I think it's annoying having to watch out for that for ourselves. - If you are in a big web app you definitely want to manage your store, so using NgRx is the best option, but the learning curve is huge and the verbose is too much. (Vuex use a simpler approach) - If you want to go to the next step and move to mobile, you have two main alternative Native Script or Ionic, but neither of them is at the React Native level. I think this is one of the strongest reasons the people choose to React instead of Angular or Vue.
@Sara-xi2ug
Just had a job interview and the interviewers were looking at me as a freak for using (and loving) Angular, can't tell how frustrating this is. I share the same views as you on Angular vs React, I remember how appalled I was at seeing html/js all mixed together with arbitrary html syntax like classname, I immediately gave up learning React and 8 years later I still feel reluctant to learn it
@rickelmonoggin
Agree, particularly on the point about Typescript. You can use Typescript with React, but it feels like it's a somewhat foreign language in the React world. The React documentation does not recognise Typescript so often you have to go looking in Stackoverflow, or blogs, or just guess, to work out what type to give a particular object. By contrast, Angular docs give you types of every single entity within its API.
@rakeshkv1170
React js reminds PHP days. That's what I think of reactjs. I agree with you :)
@daviddonadze221
Absolutly agree with you. For a large projects Angular is perfect. React can get very messy.
@souravkumarpaul
Yes I second that. Obviously it can be used but React is bit difficult for complex project.mostly it is for simple apps where you want to create components till very granular level. And the messy part is the business logic and view layer in same big file. Wherein Angular comes with very clear seperation of different layers and easy to develop.
@Enigmata23
I lean towards any framework built with Typescript. Angular and Nestjs and youre sorted. React is implementing Typescript but it is still a mess.
@mrskibum885
a talented coder can write code well in either language. i don't personally mind having the code and the html together because it allows you to do some amazing things, however i notice that new developers are eager to shoot themselves in the foot by making the render/return methods of their code to complex. even in reacts own documentation they have some poor examples of adding logic to renders which doesn't help people write good code. overall good video, i recognize that any video titled "why angular is better than react" isn't going to give react much of a chance, but i think each has it's pros/cons. happy coding!
@adodragicevic3786
I am a react developer, and I learned the basics of angular. I would be very happy if someone who is an angular developer and who likes angular could respond to my reasons for for preferring react. I'm not trying to debate on which is better. I would be grateful if I was proven wrong if I'm wrong on any of my points. Why I prefer react, compared to angular: 1. I feel working in react makes me a better vanilla JS developer, which makes the skills I gain more transferable to other technologies in the JS world. As an example, instead of using *ngFor, a directive specific for angular, in react we use .map(), a method that is part of vanilla JS! 2. React is suitable for enterprise projects if the team implements good architecture and strict conventions. TypeScript has became a norm. 3. Apparently one advantage of angular is it comes with "everything you need". However, how true is that? Angular comes with the basic things you need, like routing. Even though routing is not provided by react, it is a convention that 90% of projects use the same tool (react-router-dom) for routing. If you are using SSR, you can specialize in a framework like Next.js and then, again, you only use routing built into that framework. It is not like 10 react projects use 10 different tools for routing. When we talk about more complex things, like graph visualization, angular, of course, does not come with a built in solution for this. In fact, angular does not even have its own state management - NgRx is not maintained by the angular team (just as redux is not maintained by the react team). 4. For more complex things (e.g. graph visualization) react has a greater amount of 3rd party tools available. 5. React has a stronger community (more tutorials, youtube channels, easier to find answers, etc.) 6. Angular is named exceptionally similar to angular.js, which makes googling for answers more frustrating. 7. Functional components make code cleaner and easier to debug (because of immutable state and pure functions). 8. Angular seemed as an overkill in some ways. As example, if we want to output a string to the html, and uppercase it, angular includes an "upperacse" pipe. Why does a pipe exist, when vanilla JS has a built in .toUpperCase method? One more thing I need to learn that is not reusable outside angular. 9. React Native 10. React has less breaking changes (I am not referring to transition from angular.js to angular2, but to transition from angular 2 to higher).
@thedarkside0007
idk why would anyone choose react i can understand vue preference over angular but react and it's state management ? i dont get it
@moonswhite1409
Agree 👍
@fonziefonzarelli8049
Angular is predictable which is awesome
@Johnny1864
CLI and services FTW 👍
@divyamsharma5198
But there are very less resources available on the internet about angular and on other hand chunks of courses for learning react js
@SamaraSsr
React is the new php 😅
@DimaProsto
Exactly true !
@sanjumathew9489