4 ms·
It's pretty naive to think that Apple would somehow direct all their work towards re-writing existing code into Swift. There is literally no use case to do that
by nathanvanfleet 11y ago
It's pretty naive to think that Apple would somehow direct all their work towards re-writing existing code into Swift. There is literally no use case to do that wholesale.
Firstly, there is no question that it would generate bugs. Appkit and even iOS is old enough that you couldn't replace it completely without the behaviour changing. Even if it's fixing a weird behaviour, that would be a problem for many existing apps build on that framework.
Second of all, it would mean they wouldn't be moving forward with new features, which, basically nobody (customers even) wants.
I'm sure more and more new code will be Swift, and possibly non-framework apps can be re-written. But they won't start announcing a swap out in the next WWDC.
- pbreit 11y agoThere's one massive use case: to demonstrate to developers that it's advantageous and ready for prime-time.
- cellularmitosis 11y agoAlso, attracting and retaining talent. Talented devs are only going to stay interested in writing ObjC for so long.
- JustSomeNobody 11y agoThat statement demonstrates a rather naiive understanding of the software development life cycle. As well as how successful businesses in general behave.
- pbreit 11y agoWrong on both counts.
- manigandham 11y ago...how exactly? Companies shouldn't and don't waste time rewriting things for no reason, just to use a new language. Swift is already production ready and Apple has plenty of examples, beyond that there's nothing to "prove".
- nathanvanfleet 11y agoI don't think that use case is so massive.
- smackfu 11y agoAlso, the number of developers required to rewrite everything in Swift on a short timeframe is likely more than Apple has.