News for hackers. Stuff that matters.

A comment on Bitcode (iOS, watchOS).

Re:Bitcode (iOS, watchOS) by advanderveer on Tuesday June 09, 2015 @03:25AM (#9684470)
I find it interesting this hasn't gotten as much attention as other announcements. It seems to hand over a great deal of responsibility to Apple, at least in terms of performance. Something some might feel comfortable with or not. I can imagine this lack of control about what instructions will actually run on the hardware might not fair well with some developers?
[ Parent | on HN ]
Re:Bitcode (iOS, watchOS) by cpr on Tuesday June 09, 2015 @11:01AM (#9686303)
As long as you have (and keep updating to) the devices in question to test on, you'll have full performance info.
[ Parent | on HN ]
Re:Bitcode (iOS, watchOS) by pjmlp on Tuesday June 09, 2015 @07:50AM (#9685295)
Most likely, however this is already being done in the other mobile platforms.
[ Parent | on HN ]
Re:Bitcode (iOS, watchOS) by nly on Tuesday June 09, 2015 @10:35AM (#9686134)
Not really, you can ship native code on Android and, for Java apps, intermediate bytecode is delivered to end-user phones, not compiled in the cloud.
[ Parent | on HN ]
Re:Bitcode (iOS, watchOS) by pjmlp on Tuesday June 09, 2015 @01:27PM (#9687258)
Windows Phone 8:

http://channel9.msdn.com/Shows/Going+Deep/Mani-Ramaswamy-and...

Windows Phone 10:

http://channel9.msdn.com/Shows/Going+Deep/Inside-NET-Native

As for Android, having ART on the phone is technicality, given the platform fragmentation Google rather leaves to the OEMs the task of making ART generating the proper code.

[ Parent | on HN ]