Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

TechGod

macrumors 68040
Original poster
Feb 25, 2014
3,275
1,129
New Zealand
The reason I say this is, if Apple decides to rewrite OSX with Swift? Obviously Apple will wait it to perfect Swift a bit but once they do, do you see that happening?
 
No, OS X became about branding rather than a version number a long time ago. The difference between 10.0 and 10.9 is vastly greater than Mac OS 8 and Mac OS 9.

Really we should be on Mac OS 13 to 15 by now.
 
No, OS X became about branding rather than a version number a long time ago. The difference between 10.0 and 10.9 is vastly greater than Mac OS 8 and Mac OS 9.

Really we should be on Mac OS 13 to 15 by now.

Surely a whole rewrite of the OS should deserve a new branding?
 
Surely a whole rewrite of the OS should deserve a new branding?

That would never happen. Rewriting the whole OS in a different language would be an absolutely colossal undertaking and would only create problems.
 
That would never happen. Rewriting the whole OS in a different language would be an absolutely colossal undertaking and would only create problems.

Apple is using Swift for their apps, I assume that they will eventually rewrite the OSe's as well. They've got time don't they? they can rewrite the OSes over 3-4 years.
 
Apple is using Swift for their apps, I assume that they will eventually rewrite the OSe's as well. They've got time don't they? they can rewrite the OSes over 3-4 years.

Assuming there's a good reason to do this (there isn't) and assuming that all the code can actually be replicated in Swift (it can't), it would literally take decades to sift through all the code in OS X, rewrite it in Swift, test it, debug it, test it again, debug it again, then test it with every in-house and 3rd party application, combinations of applications, debug that, test that again, etc. There wouldn't be any benefit either, because it works just fine as it is.
 
Assuming there's a good reason to do this (there isn't) and assuming that all the code can actually be replicated in Swift (it can't), it would literally take decades to sift through all the code in OS X, rewrite it in Swift, test it, debug it, test it again, debug it again, then test it with every in-house and 3rd party application, combinations of applications, debug that, test that again, etc. There wouldn't be any benefit either, because it works just fine as it is.

Quote from Apple:

"Designed for Safety
Swift eliminates entire classes of unsafe code. Variables are always initialized before use, arrays and integers are checked for overflow, and memory is managed automatically. Syntax is tuned to make it easy to define your intent — for example, simple three-character keywords define a variable (var) or constant (let).

The safe patterns in Swift are tuned for the powerful Cocoa and Cocoa Touch APIs. Understanding and properly handling cases where objects are nil is fundamental to the frameworks, and Swift code makes this extremely easy. Adding a single character can replace what used to be an entire line of code in Objective-C. This all works together to make building iOS and Mac apps easier and safer than ever before.

Fast and Powerful
From its earliest conception, Swift was built to be fast. Using the incredibly high-performance LLVM compiler, Swift code is transformed into optimized native code, tuned to get the most out of modern Mac, iPhone, and iPad hardware. The syntax and standard library have also been tuned to make the most obvious way to write your code also perform the best.

Swift is a successor to the C and Objective-C languages. It includes low-level primitives such as types, flow control, and operators. It also provides object-oriented features such as classes, protocols, and generics, giving Cocoa and Cocoa Touch developers the performance and power they demand."

Specifically this:

Swift is a successor to the C and Objective-C languages. It includes low-level primitives such as types, flow control, and operators.

Swift is a successor to Obj-C and seems to have many benefits. A company such Apple shouldn't have any issues rewriting there OS, and testing won't take decades. A bit of an exaggeration....
 
And how long did it take iTunes to become native 64 bit? :rolleyes:
 
No, OS X became about branding rather than a version number a long time ago. The difference between 10.0 and 10.9 is vastly greater than Mac OS 8 and Mac OS 9.

Really we should be on Mac OS 13 to 15 by now.

Yeah, I tend to agree with that - "OS X" is to Apple like "Windows" is to Microsoft or "Solaris" was to Sun: I just don't see them changing it to OS XI at any time
 
Osx 11?

I can't see Apple going to OS XI as OSX has become such a brand name.

However I could see Apple possibly going from OSX 10.10 Yosemite to OSX 11 with the next release.

I mean are they really going to go to OSX 10.20 for example.
 
OS X will be rewritten in Swift when Microsoft rewrite Windows in C# and Oracle rewrite MySQL in Java.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.