oldguysrule

4 ms·

1.
by oldguysrule 12y ago
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".
2.
by oldguysrule 12y ago
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 powe
3.
by oldguysrule 12y ago
>Heartbleed. Majority of all SSL keys on the internet compromised. All ~2 billion of humans on the internet required to change their passwords due to a single mistake by a single programmer using C. You can write shit code in any languag
4.
by oldguysrule 12y ago
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 verbose. 3) Some bench
5.
by oldguysrule 12y ago
>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.
6.
by oldguysrule 12y ago
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.
7.
by oldguysrule 12y ago
>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 of work. The rise
8.
by oldguysrule 12y ago
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 Perl scripts. I l