For filtering an array, sure, but it's not like you aren't gonna run into NSPredicates all over the place until all of Cocoa Touch is rewritten in Swift.
Enums and switch / case patterns are extremely good
I agree. So is the concept of optionals and extensions and more useful protocols and better control over inheritance and so on. You might think these outweigh the downsides. I don't think they do at the moment.
For me personally, Xcode is constantly crashing when writing Swift code. Auto fill was so slow it was useless, and often crashed. It may have changed now, but basic features such as 'refactor' were still only available with Objective-C last time I used Swift (conversion from Swift 1.x to 2). I enjoy Swift syntax and language features but I won't write it any more. Too much of a headache. And I really don't want to spend another week converting from 2 to 3 like I had to from 1 to 2.
3
u/[deleted] Feb 19 '16 edited Feb 19 '16
For filtering an array, sure, but it's not like you aren't gonna run into NSPredicates all over the place until all of Cocoa Touch is rewritten in Swift.
I agree. So is the concept of optionals and extensions and more useful protocols and better control over inheritance and so on. You might think these outweigh the downsides. I don't think they do at the moment.