Another great point about React is its long-term support policy and the stability of its API. Stability is actually part of the core design principles (https://reactjs.org/docs/design-principles.html) of React. As stated on that page, Facebook itself has more than 50,000 components that use React. Because of that, Facebook tries really hard to keep the public API surface of React as stable as possible.
This does not mean that things are frozen though—far from it. What usually happens is that deprecation warnings are issued and remain until the next major release. At that point, codemod scripts are often provided to automate the bulk of the modifications needed to upgrade from a previous release to the latest and greatest. We won't cover codemods any further in this book, but you can check out the react-codemod repository (https://github.com/reactjs/react-codemod) to learn more. To summarize, upgrades are rarely a source of headaches with React because the necessary changes are automated through upgrade scripts.
Another element to keep in mind about React is that it is backed by a large corporation, just like Angular is. This can be perceived as good or bad depending on the point of view, but it certainly helps React to quickly evolve. Given the importance of React for Facebook, it is unlikely for it to be abandoned any time soon. If that happens at some point though, React will certainly continue to live on given the size of its developer community.
Let's get to know to React a little better now.