I can kinda agree with the general sentiment, but there are a lot of mistakes in this video. The biggest mistakes I can remember now: Angular can do one way binding. Angular uses Iterative DOM since version 9, which is more memory efficient than VDOM, while being compatible in runtime performance. Angular has no build in state management library, you don't have to use one one, but there are several to choose from, if you do want one. I'm less experienced in react, so don't know if everything is right for the react side.
thats just stupid.. its just a different tool. For some usecases react would just crumble into peaces. Imagine large complex tax forms. And you have a huge number of different kinds of forms. You want to reuse as much code as posible. When you chenge one input, it has to recalculate like 10 other inputs. On top of that you have to communicate with backend where user might have entered invalid value (like legislativly invalid). Belive me its huge and really complex. And a huge set of tools that angular provides - it would be really hard and painfull without them. On the other hand in a lot of different use cases angular complexity could hurt the project becouse its just not necessary. Becouse of that I think you´re full of crap.. Or just kidding.. What do I know
@Sjakub5CZ yeah you are one of them. "Change one input, it has to recalculate like other inputs." Why is that, even you don't know how to put memo before comp?? Creating forms is not a big deal. If you are bad, stick with angular and OOP. Understanding react life cycle/rules and functional programming is not easy.
@@cenkakay3506 A good developer shouldn't chose a hard to master tool, just to show that he/she can handle it. Choose the tool that fits the job and is easier to use, because you will probably have teammates of various skill ranges.
I can kinda agree with the general sentiment, but there are a lot of mistakes in this video.
The biggest mistakes I can remember now:
Angular can do one way binding.
Angular uses Iterative DOM since version 9, which is more memory efficient than VDOM, while being compatible in runtime performance.
Angular has no build in state management library, you don't have to use one one, but there are several to choose from, if you do want one.
I'm less experienced in react, so don't know if everything is right for the react side.
So what that means in angular: ?
Isn't that two way binding???
@samsondavidoff372 Yeah, but you don't have to bind two way. can as well just do [ngModel]="name" or (ngModelChange)="nameChanged($event)"
Atom as an editor option in 2024 like dude have you been living under rock
once I saw atom I had to scroll down to see the date of this video
Angular logo should be updated. And the new Angular 18+ versions are powerful and in future updates, angular will overtake react in job market.
More and more React Developer used Typescript on their projects specially to for fetch API related components.
Enterprise devs crying above legacy pure JSF frontends, backed by old Java 8 😂
You described my entire 2015 year 😀
Who uses Angular, React or Svelte, this is the question
it silly, but the the most disgusting in angular is the binding syntax : 'ng-what'.. it feel unnatural
Time to learn about Angular's Binding via Signals.
use Vue
Neither. Blazor.
Not even Microsoft uses it
If you are a mediocre developer, choose Angular, mastering React is a long and difficult process.
thats just stupid.. its just a different tool. For some usecases react would just crumble into peaces. Imagine large complex tax forms. And you have a huge number of different kinds of forms. You want to reuse as much code as posible. When you chenge one input, it has to recalculate like 10 other inputs. On top of that you have to communicate with backend where user might have entered invalid value (like legislativly invalid). Belive me its huge and really complex. And a huge set of tools that angular provides - it would be really hard and painfull without them. On the other hand in a lot of different use cases angular complexity could hurt the project becouse its just not necessary. Becouse of that I think you´re full of crap.. Or just kidding.. What do I know
@Sjakub5CZ yeah you are one of them. "Change one input, it has to recalculate like other inputs." Why is that, even you don't know how to put memo before comp?? Creating forms is not a big deal. If you are bad, stick with angular and OOP. Understanding react life cycle/rules and functional programming is not easy.
@@cenkakay3506 What do you think about vue or svelete? Same as bad? And for mediocre programmers? Are you react all the way?
@@cenkakay3506 A good developer shouldn't chose a hard to master tool, just to show that he/she can handle it.
Choose the tool that fits the job and is easier to use, because you will probably have teammates of various skill ranges.
@@saithisxI agree with you. Our job is solving the problems. Not choosing libraries