Steven Troughton-Smith points to an article by Brad Larson:
I always find it more effective to learn new programming concepts by building projects using them, so I decided to do the same for Apple’s new Swift language. I also wanted to see how well it would interact with my open source GPUImage framework. As a result, I made GPUImage fully Swift-compatible and I’ve built and committed to the GitHub repository a couple of Swift sample applications. I wanted to write down some of the things that I learned when building these.
It’s interesting to see programmers get their hands dirty with what most likely will be the way forward for iOS developers.
I might be the only person on earth who actually likes Objective-C… I find the syntax clean and logical, I realise that I only use C/C++ and Objective-C on a regular basis, so I’m pretty much biased towards the “C Style Syntax”. But I really can’t follow Swift syntax, it seems confused and awkward…
Almost every language that is different than the one you use will feel that way.
Lots of people like Objective C. The guy that runs Nerd Ranch LOVES Objective C but then he also makes a living out of teaching it. So it might be a little of he loves it and a little of he makes a living teaching it. I don’t know him personally so I don’t know.
I’ve programs in about a dozen languages from COBOL and FORTRAN to various version of basic including VB, C, C++ and Objective C. All have their good things and all have their bad things.
Yeah, I guess you are right. I’m just being a Luddite.
I hope Objective-C hangs around for a while on the Apple platform, I really enjoy using it.
I like the core of the language, now that some of the more recent features have been added. However I will be glad to see the backside of header files, @interface sections (the contract can and should be inferred from the implementation), etc
Apple could and should have addressed those things a decade ago…