And quite a bit behind in flexibility and dynamism. Giant step backwards. Vtables? I don't think so. override keywords? WTF? Its not so much they removed the C as the "Object".
Dynamic typing is not "type unsafe". Objective C objects are completely "type safe". They are actually true objects in that they can receive and potentially handle any message sent to them. This is an advanced but…
1) So was Java for a bit. It sucked. Developers ignored it. 2) UIApplication.sharedApplication.delegate vs UIApplication.sharedApplication().delegate - nope. It isn’t more concise. It appears to be a wee bit more…
>Unlike C and Objective-C, Swift enumeration members are not assigned a default integer value when they are created Well that’s gonna make storing persistent values tricky.
Objective C isn’t going anywhere. Swift is shit. I suspect it will die in a couple years, like the misguided effort to get people to adopt the Java bridge or WebScript before that.
>At least Google had the decency to pick a language everybody was already using and use that. If you think Java is remotely comparable in power and expressiveness to Objective C, you should probably reconsider your line…
I got started with WebObjects, a Next product a couple years before Apple bought them. Yes I've written wonderfully powerful web applications in Objective-C back when the rest of the web was being built using CGI and…
And quite a bit behind in flexibility and dynamism. Giant step backwards. Vtables? I don't think so. override keywords? WTF? Its not so much they removed the C as the "Object".
Dynamic typing is not "type unsafe". Objective C objects are completely "type safe". They are actually true objects in that they can receive and potentially handle any message sent to them. This is an advanced but…
1) So was Java for a bit. It sucked. Developers ignored it. 2) UIApplication.sharedApplication.delegate vs UIApplication.sharedApplication().delegate - nope. It isn’t more concise. It appears to be a wee bit more…
>Unlike C and Objective-C, Swift enumeration members are not assigned a default integer value when they are created Well that’s gonna make storing persistent values tricky.
Objective C isn’t going anywhere. Swift is shit. I suspect it will die in a couple years, like the misguided effort to get people to adopt the Java bridge or WebScript before that.
>At least Google had the decency to pick a language everybody was already using and use that. If you think Java is remotely comparable in power and expressiveness to Objective C, you should probably reconsider your line…
I got started with WebObjects, a Next product a couple years before Apple bought them. Yes I've written wonderfully powerful web applications in Objective-C back when the rest of the web was being built using CGI and…