“Craig Federighi revealed many interesting tidbits when you read the transcript – and read between the lines – of his talk with John Gruber of Daring Fireball on The Talk Show podcast,” Lou Miranda blogs.
“Here’s a quote from Federighi on where Apple is directing its efforts: ‘the team that does the Dock and the window management on OS X, implemented all their new features for El Capitan in Swift and started mass-converting all of their code,'” Miranda writes. “Well, it sounds like Federighi is saying that’s what Apple’s developers have just converted to Swift.”
“How convenient – it could also be adapted at the same time to iOS and the ARM chip architecture,” Miranda writes. “Hmmm.”
Read more in the full article here.
MacDailyNews Take: Hmmm, indeed.
I don’t get the Hmmm. If the code was previously written in Objective-C, it could also be compiled to run on ARM devices. That means there is nothing new here. However, by migrating more Objective-C code to Swift, Apple could make some limited performance gain (always nice) and use the opportunity to revisit and clean-up their code.
It can be compiled to run Intel and/or ARM. And, if you do some reading about the connections between Swift and its compiler… Some very interesting inferences can be made.
Plenty of interesting reason to use Swift.
Suggested to read up on why.
Here’s a good article.
http://arstechnica.com/apple/2014/10/os-x-10-10/22/
I hope they rewrite iTunes from the ground up in Swift.
Yeah, but that wouldn’t solve the prime problem: The multi-tentacled MONSTER that is the GUI of iTunes.
If Swift lives up to its ‘promise’ of actually stopping memory buffer overruns, the programming language is a generous gift to the world from Apple.
The vast majority of security holes in software are caused specifically by induced memory buffer overruns. They are literally THE PLAGUE of programming in our current era.