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

recoil80

macrumors 68040
Jul 16, 2014
3,117
2,756
I guess they'll move to 64bit in 2016 but I'm not sure they'll allow Swift-only apps so soon. Since the language is new I expect Objective C to be popular for some more years before it will be discontinued.
 

mazz0

macrumors 68040
Mar 23, 2011
3,283
3,769
Leeds, UK
I guess they'll move to 64bit in 2016 but I'm not sure they'll allow Swift-only apps so soon. Since the language is new I expect Objective C to be popular for some more years before it will be discontinued.

I find it incredible that anyone would prefer to programme in Objective C. Yuck. Swift: yummy.

I don't see them dropping support for old apps any time soon, I think it's more likely they'll do something clever in software to control the disk and memory usage concerns (in fact I seem to recall reading something along those lines not so long ago that would lead to reduced app sizes).
 

PsykX

macrumors 68030
Sep 16, 2006
2,745
3,922
Using Swift would be very beneficial. In fact, Apple should begin the process of converting all the native apps into Swift to boost iOS performance.

That's the first thing that came to mind when the rumour mill started saying iOS 9 would focus on optimizations and whatnot. The native apps that Apple has don't do much and wouldn't be long to convert.
 

Andres Cantu

macrumors 68040
Original poster
May 31, 2015
3,327
8,002
Texas
That's the first thing that came to mind when the rumour mill started saying iOS 9 would focus on optimizations and whatnot. The native apps that Apple has don't do much and wouldn't be long to convert.
Yeah, I see them moving to Swift today for their own apps, but for third-party apps, I think they will do it later (in a similar fashion as the current requirement for app updates to be 64-bit compatible and the time it took as well).
 

GreyOS

macrumors 68040
Apr 12, 2012
3,358
1,694
That's the first thing that came to mind when the rumour mill started saying iOS 9 would focus on optimizations and whatnot. The native apps that Apple has don't do much and wouldn't be long to convert.
how will converting the source code to swift optimise it?

my understand is that swift is just a higher level language which makes coding easier and quicker, but generally these higher level languages are harder to optimise. for apple developers, i find it very unlikely that there will be much to gain from moving to swift, and it may in fact make it worse..?

not saying they won't convert apps to swift to make it easier to maintain and so on, but i don't think you're going to see any optimisations...
 

PsykX

macrumors 68030
Sep 16, 2006
2,745
3,922
how will converting the source code to swift optimise it?

my understand is that swift is just a higher level language which makes coding easier and quicker, but generally these higher level languages are harder to optimise. for apple developers, i find it very unlikely that there will be much to gain from moving to swift, and it may in fact make it worse..?

not saying they won't convert apps to swift to make it easier to maintain and so on, but i don't think you're going to see any optimisations...

You're not wrong about Swift being easier and quicker to develop, but there has been a few slides last year about how Swift was faster than other languages out there :

wcdXk.jpg
 
  • Like
Reactions: 0815

GreyOS

macrumors 68040
Apr 12, 2012
3,358
1,694
You're not wrong about Swift being easier and quicker to develop, but there has been a few slides last year about how Swift was faster than other languages out there :

wcdXk.jpg
cheers!
 

recoil80

macrumors 68040
Jul 16, 2014
3,117
2,756
I find it incredible that anyone would prefer to programme in Objective C. Yuck. Swift: yummy.

I like Swift but like many other developers I have plenty of Objective C libraries and I don't want to be forced to upgrade them to Swift in a short period of time.
The new developments are made in Swift, but legacy code has to be supported for a few years.
 

Andres Cantu

macrumors 68040
Original poster
May 31, 2015
3,327
8,002
Texas
I like Swift but like many other developers I have plenty of Objective C libraries and I don't want to be forced to upgrade them to Swift in a short period of time.
The new developments are made in Swift, but legacy code has to be supported for a few years.
I'm sure it will be supported for a few years like you said.
 

Andres Cantu

macrumors 68040
Original poster
May 31, 2015
3,327
8,002
Texas
Looks like no transition this time, but it'll probably happen next year and take a whole year (meaning iOS 10 will likely support A6 devices).
 

mazz0

macrumors 68040
Mar 23, 2011
3,283
3,769
Leeds, UK
I like Swift but like many other developers I have plenty of Objective C libraries and I don't want to be forced to upgrade them to Swift in a short period of time.
The new developments are made in Swift, but legacy code has to be supported for a few years.

True. Of course, I'd happily spend a few weeks porting all my code, provided there was no deadline. I think that would be a pleasant way to spend some time :)
 

terryk

macrumors newbie
May 7, 2015
5
0
I don't think so.
The transform to 64 bit seems reasonable, and obviously the iOS X will be a big leap.
But Apple is still selling 32 bit iOS device now: Apple TV, ipod touch 5th generation, iphone 5c. I don't think apple will drop them so fast.
 

mazz0

macrumors 68040
Mar 23, 2011
3,283
3,769
Leeds, UK
to be clear to others he is saying developers will be able to submit just a 64 bit app without a 32 bit version- previously they had to do both.

it doesn't mean they can only submit a 64 bit app and aren't allowed to submit s 32 bit app too.

Does it say why you'd want to do so? If it meant smaller bundles and what not then I can sort of see why it might be useful (though not really, how much size is really taken up by the code compared to other resources?), but doesn't App Thinning take care of that anyway?
 

GreyOS

macrumors 68040
Apr 12, 2012
3,358
1,694
Does it say why you'd want to do so? If it meant smaller bundles and what not then I can sort of see why it might be useful (though not really, how much size is really taken up by the code compared to other resources?), but doesn't App Thinning take care of that anyway?
i plan to watch it (and some other dev vids) more closely later, but i think it's because certain 'cutting edge' development features and APIs (like metal) are only available in 64 bit. so in cases where targeting both 32 bit and 64 bit actually require two different code solutions, this would free up some developers to focus on just 64 bit. (i'm guessing most simple apps don't need to change their code to build in both 32 bit and 64 bit though)
 

TWD98j

macrumors 6502
Sep 14, 2010
264
49
I think an announcement of this nature would be more likely to be made in the fall when the new iPhone(s) is(are) announced. Right now, with Apple still selling the 5C, which is A6 based, making such an announcement doesn't make a whole lot of business sense.

However, come the fall, when Apple will most likely eliminate the 5C from the lineup, such an announcement becomes more tangible. At that point, they will likely drop the 5S to the low end model and then be able to boast an iPhone lineup that is "entirely 64 bit". Then they could make the same announcement regarding their iPad lineup the following month, if they choose to eliminate the original iPad mini.

But yeah, I can see such announcements coming very soon.
 

Andres Cantu

macrumors 68040
Original poster
May 31, 2015
3,327
8,002
Texas
I think an announcement of this nature would be more likely to be made in the fall when the new iPhone(s) is(are) announced. Right now, with Apple still selling the 5C, which is A6 based, making such an announcement doesn't make a whole lot of business sense.

However, come the fall, when Apple will most likely eliminate the 5C from the lineup, such an announcement becomes more tangible. At that point, they will likely drop the 5S to the low end model and then be able to boast an iPhone lineup that is "entirely 64 bit". Then they could make the same announcement regarding their iPad lineup the following month, if they choose to eliminate the original iPad mini.

But yeah, I can see such announcements coming very soon.
I agree, that makes much sense. I'm just curious to see their upcoming iPhone lineup, as we haven't had any physical leaks about the "C" or "S" models, and we're unsure whether they're looking for all models to include Apple Pay.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.