3 ms·
Sure, if it's a good old whole-program-crash either way, that means they're equivalent severity. It's not my intention to softball Swift with some nebulous idea
by MaxBarraclough 8y ago
Sure, if it's a good old whole-program-crash either way, that means they're equivalent severity. It's not my intention to softball Swift with some nebulous idea of what counts as a proper 'fundamental' bug.
In defence of Swift, it could still be that they spent less time bug-hunting than when they were developing in Objective-C, to reach the same, or inferior, level of program correctness.
Also, we're comparing a new product to a mature one. Were the original Objective-C programs stable in their first release?
- LeoNatan25 8y agoMy point isn’t to say Swift is bad. I personally don’t like it, but that isn’t the point. In my original comment, I wanted to say that rewriting software just because of a new language is probably a bad idea. Apple could have continued using the existing software, rather than just throw away stable code for the sake of new devs to use a new language.
- MaxBarraclough 8y agoAgree completely - I'm not convinced that Swift is so much better than Objective-C that it makes sense to throw out mature production code. Mandatory link to Spolsky's blog post on exactly this: https://www.joelonsoftware.com/2000/04/06/things-you-should-never-do-part-i/ https://www.joelonsoftware.com/2000/04/06/things-you-should-...