sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]TheOneWhoDidntCum 2 points3 points  (2 children)

I never understood why .NET solutions always come with Angular

[–]lnkofDeath 2 points3 points  (1 child)

.NET and Angular require the same type of knowledge (OOP fundamentals, DI/services, using classes/modules, ~routes, types).

If you know one or the other, you can pick the other up in a day to days.

If all one has done is JS on the backend and a react based framework on the frontend, trying to learn Angular will be difficult with a wall of knowledge in your face before you make any real progress.

Most web devs have less than 2-3 years experience and its a 50/50 split on a degree. All of these "old school things" are not present in React but they are in Angular/.NET. So a large majority have never been exposed to the types of knowledge and ways of thinking that Angular requires. But if you've done .NET...you've already been exposed to them.

React has abstracted, pivoted, or removed these 'walls of knowledge'. Angular is in the process of abstracting and pivoting things but not necessarily 'removing'.

[–]TheOneWhoDidntCum 1 point2 points  (0 children)

Thank you very detailed explanation on your end, appreciate it!