8 ms·
One more blow to the head for objective-c. Wonder if this the final nail in the coffin.
by checker659 7y ago
One more blow to the head for objective-c. Wonder if this the final nail in the coffin.
- mmargerum 7y agoIt certainly gives me a reason to migrate now. Swift alone wasn't enough of a reason.
- protomyth 7y agoGiven that Craig Federighi basically said this type of migration only comes around every 20 years, I would imagine Objective-C is dead. I do hope they actually take the time and fix the Swift examples so they are updated. This does hurt. I've been programming Objective-C since NeXTSTEP and love it. Swift is still like Perl for me. Something I will use for programming for money, but not enjoy for one minute. I loved the clarity of selector syntax, but Javascript clones rule the world. I still don't understand the love of commas or why they are needed.
- adamnemecek 7y agoHow is swift a javascript clone? Objective c is insanely verbose.
- protomyth 7y agoHow is swift a javascript clone? They ditched the selector syntax and went to a Javascript / C++ like syntax. There were so many ways to keep the selector syntax, but they went conformist. Objective c is insanely verbose. well, no - Swift's call syntax actually results in the same or more characters: somePoint.moveBy(x: 2.0, y: 3.0) [somePoint moveByX: 2.0 y: 3.0]; somePoint.moveBy(x: 2.0, y: 3.0, z: 4.0) [somePoint moveByX: 2.0 y: 3.0 z: 4.0]; Swift benefited from some shortening of the method names that can be equally applied to Objective-C. Plus, why the whole split by a left parentheses and comma thing?
- steve1977 7y agoI feel you. I understand that Apple tries to cater to the "web developer" crowd as well, but sometimes this feels like a regression compared to what OPENSTEP was about.
- pzo 7y agoFinal blow at least for me will be at least some minimal interop with c++ (instead of just c) and sort of reflection mechanism.