Ember never made it to that point and almost certainly never will. People are still free to use it of course, but it’s going to be a poor technology choice in light of the above factors.
I personally feel productive with Ember, but the custom object models and getters and setters for everything are a bit of a turn off, especially after working on an Angular project recently with typescript support. Mobx, for instance, seems to be able to accomplish similar things as Ember but without the custom object model and getters/setters.
[1] For those wondering, Glimmer is Ember's next iteration of view layer and rendering engine, pulled out into a separate library. It's built from the ground up (and so isn't subject to backwards compatibility with Ember just yet), uses typescript, is component based, and it compiles down to op-codes that are used to update the DOM instead of DOM-diffing. http://glimmerjs.com/
There are a few reasons for this. First, Angular’s programming model lends itself to typical enterprise software requirements. Secondly, Angular, and TypeScript in particular, is similar to what enterprise programmers are typically used to (namely Java and C#). There also is Ionic, which is largely based on Angular.
Finally, Angular and React is one of those odd cases of regional variation in technology distribution. React appears to be more popular in the US, particularly with Silicon Valley companies, than in Europe.
Job postings on job boards, or talking with real people from real companies asking for and ready to pay for the skill? The perception of what is needed could be skewed by someone investing more in postings, recruitment spam is notorious as well.
Basically they didn't jump on the React bandwagon because of the licensing thing, but are ready to jump on Angular's because it ticks all their boxes