Moving from Angular to React. Trend or not?

Question

Angular

Good afternoon
I'm not a frontend developer myself, but I'm interested in the topic.
Very often I see something like this in vacancies: "We are currently using angular, but we plan to switch to react"
Is this some kind of trend?
Why are companies moving away from Angular? A consequence of high complexity and redundancy for most projects?

Answer 1

Answer 2

React is a library, and Angular is a whole framework. If you're in the enterprise space, it's easier to choose Angular as it already has what it takes to architect a huge web application and maintain code later on. When huge applications start to be written in react, it looks like a hodgepodge of npm packages (the same redax, sledge, axios, flow, react router). I do not argue that you can also create large applications on react, but this will require more effort (with the same knowledge of frameworks). Why? Yes, because in Angular with typescript and the architecture that Angular imposes on developers, you can apply classic design patterns that were previously used in classic languages ​​such as Java or C#. They can also be used in regular js, but there is not much sense in this, since classical patterns are tied to OOP and static typing. Why are patterns needed? To maintain the code. In our company, projects have been supported for several years (I know projects that have been supported for more than 5 years) and other people are involved in the project. Someone is removed, someone is connected. And when you need to maintain the code, then the typescript and the angular architecture just right allow you to do all this painlessly (provided that the code is written well). All this, I'm not afraid of the word, "vyser", which was written by a colleague above, in the direction of Angular is due to the fact that Angular has a higher entry threshold than other frameworks. And so people think that there is some kind of magic going on there. And it turns out that people do not understand what is happening there and complain that it is too complicated, but everything is simple in React. In React, everything is much simpler. To write in React, you basically have enough knowledge of es6. What can not be said about Angular. Because there is a typescript and rxjs, which simply cannot be understood, you need to try hard to start thinking in streams and how to work with them. But when you start to understand how rxjs works, how Angular itself works (change detection, for example), it becomes simply unimaginably easy to write code. The whole hatred is in the direction of angular due to the fact that the frontend did not initially exist as such. After all, there was php and it worked fine with html. Then there were templating engines and jquery. All this was done by backenders and there was no frontend as such. And then there were frameworks like angular, which took over most of the logic and the backend turned into a REST API. The frontend was not complicated, Angular took over a significant part of the logic and thereby complicated the frontend, therefore, those who are used to typesetting molds cannot master these tons of abstractions. On some kind of freelance or medium-sized projects, there is no point in angular, which is why react and view are used there, well, jikvery, where would it be without it. And if the project is at the level of 50-100K dollars, then there is no talk of any zhikveri.

Answer 3

About 2-3 years ago, the angular from the top framework sank into shit, and no one will do new projects on it, those who have a thousand times rewritten legacy try to get down to react or view.
If you look at the overall market (which is generally a year behind the development trends), then in 2016 the number of vacancies for angular / react became equal, although the year was 95/5. Now it's more like 5/95, and that's good. There are two great different alternatives that can also be used with typescript.
Fresh satire on the topic - https://hackernoon.com/why-angular-made-me-quit-we...

Answer 4

as a result of the success of marketers of one or the other camp.
and fashion changes.
want advice from an engineer? "Uzbogoitez" and stop looking for the meaning of cockroach races in the minds of fashion lovers. the fashion for react is already passing; fap on vue will end in a year, giving way to another "revelation", which in turn will die, supplanted by another fap according to a new revelation.
and it will happen faster than you can even understand the difference between "obsolete" and "most trendy".
and to the question "why abandon the obsolete, if it works and performs the tasks we need" - no one will clearly, technically justified answer you. they will start rubbing you game about syntactic sugar, about the "correct" implementation of mvc, about reactive coupling and that it is better everywhere (believe me, not everywhere), that this is the "correct magic" and a more progressive approach, etc. etc.
but no one, no one can give you at least some technical justification, and intelligible reasons. (the last technically sound decision was the transition to typescript in the node, because, thank heavens, they finally began to realize that dynamic typing in large projects will not go far. You see, in 5 years they will grow up to understand the reasons why Java is nowhere not going away from the enterprise sector and servers in business systems .. but that's not the point)
well, the difference between 99% of javascript frameworks is a bunch of nonsense and stories about how everything is cool, progressive, youthful. and virtually nothing technically sound. yes, the structures are different, the api is different, but this difference usually reflects only the taste of their authors and very rarely has at least some kind of technical necessity.
because it is FASHION.
"Don't try to understand cockroaches."
and companies that add lines that confuse you to job descriptions - most likely do not plan to change technologies. changing technology on a large product is most often not only technically stupid, but also financially costly. no manager in his right mind and solid memory will not do this without good reason.
they are only trying to increase the pool of potential applicants and the attractiveness of the vacancy in the eyes of the unreasonable.
they hope that fashionistas who follow trends but remain on "old technologies" will be tempted to change jobs under the promise that they will smoothly merge into the new framework, at the new job.
... ps: while jQuery continues and continues to do 90% of all the dirty work on 90% of all sites ;)

Answer 5

Yes, I also came across this phrase. When asked what, in fact, the matter was, the answer was that there is an admin panel in angular and there is a main site in react. And some other one was also started on the reactor. Well, "sometime in the near future" and the admin panel will be changed from angular to react, it has taken root better in the office. In the meantime, there are tasks here and there.
In general, of course, soon everyone will write on a blazer :) to hell with these js-frameworks )