All of these problems could be solved by a company with Apple's resources if they wanted the problems solved.
Need more developers? Hire more.
Payscale problems? Pay your developers what they are worth to you. Of course, if they aren't worth much to you, then this point is moot.
Retention problems? Addressed by both points one and two.
That they do not use their resources to solve these problems says more than the fact that they have these problems.
>ed more developers? Hire more.
They're aiming to increase their total number of Cupertino employees from 16k to over 24k in 2016. For any organisation, absorbing another 7k+ employess is no mean feat.
Apple is experiencing unprecedented success and fantastic growth. But sure, that's trivial to manage. You could do it in your sleep. Maybe you should drop Tim Cook an email.
While they have money, their pay scale isn't famous for being extravagant. People work there mostly for prestige, but you can get money and prestige working for a startup.
Cook has said publicly that their biggest challenge is talent retention. They're obviously short-handed on OS releases, and willing to reallocate when necessary. So it is not surprising to me at all (but deeply disappointing) that Safari improvements would take a backseat.