It's funny how everyone says they like React because "it's easier to learn", but employers only want to hire people with multiple years of React experience. Whereas with Angular, you just watch the 20-hour video tutorial and then at the end of the week you know it. As someone who mostly uses Angular on the front end, it feels like I'm trapped in the movie Idiocracy.
I'm someone who was pretty embedded in the AngularJS/Angular ecosystem for 5 years before (I was a major contributor to the open source ecosystem & was an early pioneer/advocate of some of the views that became common), and the past 4 years I've almost exclusively been working on React apps. There are a lot of things that I see in the React ecosystem that have been huge mistakes - prevalence of react-router, the worst router I've ever worked with minus Ember's, form story being generally awful/full of awkward APIs in libraries, react-query & overuse of hooks/context over something sane like rxjs to encapsulate async logic, hooks themselves being full of magic and needing your code to be written in certain ways sometimes terribly to satisfy opaque flow instead of something more explicit, and the testing story being filled with too much mantra about being integration test heavy instead of breaking up code to be lighter on integration tests, resulting in too many component tests being too integrated and breaking all the time/flaky as a consequence of the lack of focus. I miss Angular when it comes to a lot of these aspects some days, but I hated the DX story in Angular (it definitely got worse from AngularJS to Angular).
I feel like the frontend world could do better than both React and Angular, but I don't feel like the other options available solves the union of problems, and I don't feel React is positioned to solve its problems, and Angular's problems seem limited by the personnel/leadership involved as well.
You really think Ember has the worst router? I'm the exact opposite. But maybe we used different versions of it I suppose, since it was overhauled a couple of times I think.
Agreed about rxjs though. Very underutilized outside of Angular unfortunately.
There are 34 hours of video. But if you skip the exercises, which imho are unnecessary, it's about 28 hours. And if you watch the remaining videos at 1.5x speed, that's like 17.5 hours. Even less if you skip some of the optional sections. So realistically probably a little over 20 hours if you're constantly pausing to take notes, but still not bad at all. And certainly not something that should take multiple years to learn, given that you should be more-or-less up to full speed within a few weeks of starting to actually build stuff after watching the course.
