Re:Beyond Objective-C, Beyond Swift
by TheOtherHobbes on Saturday September 27, 2014 @10:01PM
(#8378724)
>This is almost certainly a library issue rather than a language issue.
Is Cocoa a language or a library?
IMO the criticisms really apply to Cocoa, not Swift.
Or rather - they're complaints about the fact that Swift could have been designed to simplify common Cocoa boilerplate, but instead it seems to be Yet Another Blub (c) 2014.
What's going to have more of an influence on developer productivity - a novel type inference scheme, or an OS API that works so well you don't need to keep writing the same boilerplate over and over, or go looking for 3rd party libraries to fix its deficiencies?
Is Cocoa a language or a library?
IMO the criticisms really apply to Cocoa, not Swift.
Or rather - they're complaints about the fact that Swift could have been designed to simplify common Cocoa boilerplate, but instead it seems to be Yet Another Blub (c) 2014.
What's going to have more of an influence on developer productivity - a novel type inference scheme, or an OS API that works so well you don't need to keep writing the same boilerplate over and over, or go looking for 3rd party libraries to fix its deficiencies?