Working overtime is nothing new, but transferring a team from one OS to another is (even though it has precedent). All the time the OS X team spends on iOS is time that could have been used to further progress OS X along, and there is a lot of work that needs to get done. Given how many issues need work on, hiring more people would be helpful here. If it was a single problem, fine, more hands don't always help. But when you have hundreds of issues requiring major work, well then hiring more people is more often than not the solution.
Completely wrong. Software development companies do this all the time. They sometimes move people from one project to another during crunch mode. I am willing to bet Google, Microsoft, Samsung, you name it, all do it on some projects.
Hiring from outside? Apple not? According to their "Job Opportunities Page" and using the filter "Software Engineering" it says it is showing 600+ results. Sounds like they hiring to me. Though yes Apple is a HUGE company.
They can't just take someone off the street. I've already made a long post on another topic here discussing that. Here is a copy and paste of most of it.
Sadly it is not that easy. No matter if they have a Computer Science degree, or even if they were a Doctor of Computer Science (though for a project like this, that wouldn't be "special" to have) and had 5+ years of industry experience you can't just hire someone off the street and the next day they can jump right into this big project that is entering crunch mode and whip off code like that
1: You interview them, and interview a lot of people. That can be a long process. I'll just skip it and pretend it was instant.
2: You agree to hire them and officially offer the job. They accept.
3: What if they already were employed at a place and needed to give at least 2 weeks to a months notice? Well you wait longer. Or worse, what if they weren't local and had to move (though for an important position you need filled fast you would be looking local first).
4: Ok, now let's say only after a week of offering them the job they start. What now? Start work? Not quite
5: Get familiar with the code base/get setup. Every single development company has their own way of doing this. The new coder has to get familiar with their technology, their coding style, and more. Matter of fact they are still more than likely reading and studying the manual that all coders for the company most follow. This follows coding styles and guidlines to make it easier.
6: Familiar with the project. How is the design of the project? What are they expecting? Where are they currently at, working on, needing done?
I can go on on. More than likely they haven't even started any "real" coding work for the project. They haven't put them on the biggest task yet. They are getting used to the coding style, guidelines and the technology being used on the project. Even their internal libraries they have to learn.
You expect someone off the street to just jump right in and be able to implement features and fix bugs without any prior experience of the code base? Nope.
You move from within. They have experience with the style, guidelines, internal code libraries, technology and more. They know what is expected. Their is virtually zero setup time.
I could go on and on. But the fact is every company does this. I am so confused why people all of a sudden thing Apple is absolutely lost and they think they are just some random start up software company. Even Steve Jobs (since everyone here, not saying or implying you, thinks he was God and was the only one who could manage Apple) made it clear to the public that he did move people around to different projects when needed. And no, I'm not talking about the whole Mac Vs. Lisa and the Mac team being pirates and all that.
Is it "time loss" on the OSX Project? Maybe. But who knows. We don't know the state of that right now. Just because it wasn't announced when it usually is doesn't mean anything. Apple has before decided to release products later, even if they weren't "late" or having issues. Maybe the OSX Project is doing great? Maybe they are even ahead of schedule (though in software development you never are even if you think you are)? Maybe their internal deadline isn't nearly as hard or complicated as what could be set for iOS7? Fact is none of us know really. It isn't announced. This could be exactly what Apple is doing or planning on release dates/announcement dates.