Re:An ARM-based MacBook SE could destroy Chromebooks and mid...
by grey-area on Monday April 27, 2020 @02:37AM
(#22993451)
Yes, as they eventually did with the OS X transition, the 64bit transition etc
They'll support older apps for a long time though, it just won't be the preferred sdk and will gradually be phased out.
The situation they have right now is madness - two parallel slightly different UI toolkits and SDKs, one of which makes vastly more money.
Re:An ARM-based MacBook SE could destroy Chromebooks and mid...
by Hamuko on Monday April 27, 2020 @04:58AM
(#22994142)
>two parallel slightly different UI toolkits and SDKs, one of which makes vastly more money.
And one which has a longer history. Should every Cocoa application be written in UIKit to continue working?
Re:An ARM-based MacBook SE could destroy Chromebooks and mid...
by grey-area on Monday April 27, 2020 @05:09AM
(#22994204)
Yes, in the same way as all Pascal apps had to be rewritten to the C API a long time ago, and all Mac OS 9 apps had to be rewritten as cocoa (NextStep), or all Objective-C apps will have to be rewritten as Swift as that is the new blessed SDK. In practice it won't be a huge burden as older apps will not be phased out for a long time - see the Objective-C to Swift transition - there will be a very long transition period.
I'm not saying this is great for developers, I'm saying it makes economic sense for Apple and the signs are they are moving in this direction.
And just outright kill a bunch of applications?