4 ms·
Sure, I don't disagree. Though, look at QuickTime for example. That was deprecated in Mavericks, but it's going to be around for another few releases. AVFoun
by jawngee 12y ago
Sure, I don't disagree.
Though, look at QuickTime for example. That was deprecated in Mavericks, but it's going to be around for another few releases. AVFoundation (the framework I use the most) is used by FinalCut, iMovie, etc. so porting that isn't straight forward because it would break so much stuff. So I do think you'll see deprecation of certain things as maybe they move to design patterns that are a better fit for Swift, but entirely replacing AVFoundation would be straight up insane when it works so well (as long as you are doing everything by the rules laid out in a largely unwritten book).
- LinaLauneBaer 12y agoOne of the reasons why QTKit sticks around is that it has been around since 10.3 and it's foundation is even older going back to I think 1992. So I think QTKit is an edge case and probably not used by a ton of developers directly. I think the 80/20 rules also applies here... by porting 20% of the frameworks you get 80% of the functionality. That being said: I think that if it happens it will happen over time. Deprecating something in Mavericks does not mean that it has to be gone in the release after Mavericks. GC was with us for way too long... But you can replace almost anything within lets say 5-7 years. That would be 5-7 major releases.
- LinaLauneBaer 12y agobtw nice app