Cost much for Apple to buy the name from Cisco?
They probably will eventually...
Cisco isn't going to sell the name that they've been using for decades.
Cost much for Apple to buy the name from Cisco?
They probably will eventually...
Cash is not the resource Jobs is talking about. It’s the people. If you listen to the end of the WWDC keynote, it is very noticeable that several of the former/current “Mac centric" teams worked on iPhone 4.
That’s very telling. These teams are busy with iDevices at the moment, and while I’m sure there are things happening on the Mac side they’re not top priority.
It’s not quite as bad as the Mac vs. Apple II separation during the 80’s, but there’s a priority list for sure.
If you were hired as a developer or engineer at Apple tomorrow, which team would you want to work for?![]()
There shouldn't be a conflict at all because a cell phone and a giant iPod Touch have little in common with a full blown desktop Mac.
This one bit I've quoted shows just how little you understand of systems design, and why iOS was so capable right out of the gate.
You're right. The iDevice continuum shares virtually nothing with the desktop Mac continuum.
Except for virtually everything below the layout of the interface layer.
Seriously, that's about the only aspect of iOS that isn't shared with Mac OS X. They're not being pulled *off* OS X to work on iOS, they're being told that the current priority is iDevice-focused work.
It's the same code-base, and that's something you should be thankful for.
Virtually every code change made to ensure performance is acceptable on an iPhone or iPad will make the corresponding subsystem run like greased lightning on something with as much beef as a MacBook Air or Mac Pro.
Was wondering how this would play outGlad to see Apple took care of things ahead of time, unlike last time around.
And there's more:
Are you implying there aren't people out there that would be qualified to hire/train to do these things?
...
Otherwise, it seems you are implying that only a select few people in the entire world are qualified to work on operating systems and they are busy with iOS. I simply would have to disagree with such an implication.
Please. There are things from OSX in iOS, but I see absolutely NOTHING coming FROM iOS in OSX. Name even ONE thing or spare me the lecture.
I wonder how many times I have to say that this would not be an issue if they would just hire more people so that they don't have to put a "priority" on one or the other. But that just doesn't sink in. Some people would rather argue for months on end than admit the other person has a good point.
That’s exactly what Jobs thinks. Apple hires a certain type of person that meets their internal requirements as an employee.
It doesn’t matter how many resources you have (employees, cash, etc). Resources are always going to be scarce, and priorities will always exist. That’s how businesses are run.
I guess we'll just have to disagree then. We have historic unemployment numbers and MANY of those are in computer science. Telling me that none are "good enough" for Apple is completely absurd, IMO, particularly when from the employees standpoint, Steve will fire them for looking at him funny (or rather some mysteriously jump out windows?). OSX isn't rocket science. It's Computer Science and there is a plethora of unemployed qualified people out there and Apple has the cash to hire more employees. It really is just that simple.
http://store.apple.com/us/configure/MB953LL/A?mco=MTM3NDc2NjANot one iMac even has a quad-core available for it yet
I am right. It does not have a THING to do with desktop or notebook HARDWARE. NOTHING. The FACT is that Mac Pro hardware is completely out of date. Not one iMac even has a quad-core available for it yet and you're telling me that it is the right move for Apple to delay their Mac products and push forward with cell phones and tablets that require another computer to even operate.![]()
I have had a quad core i7 in my 27" iMac since November.
You're right. My mistake. I was thinking about the Macbooks.