@Transition
Best of luck!
@karlos give Objective-C a chance... If this trend continues it will likely be one of the dominant programming languages of the future
I sincerely hope not. It's the nastiest bastardisation of two perfectly reasonable but utterly unrelated syntaxes I've ever seen. It truly deserved to be drowned a birth, but unfortunately we weren't so lucky. The day that particular brand of syntactical lunacy becomes a "dominant programming language" is the day I resurrect my career as a chemist.
But it's not like that, Obj-C sits above the language, it's more a feature of the OS than the language...
It is like that. That mush that disgusted you so much
is the language. The fact that you've had to mentally separate the concept from the implementation is a direct consequence of the fact that it has such a failed union of unrelated syntaxes. What you are basically saying is, it's like this "ultra cool OS feature that sits above the language and lets you do cool stuff". Well, sure, it might be
like that once you've conditioned yourself into viewing it that way, but it most assuredly
isn't that. That would be a custom pre-processor for C provided by the OS. However, Objective-C is not a C preprocessor, it is a language and one that pre-dates apple's interest in it. The fact that you have to view it as a separate entity floating above C "to get it" is precisely what's wrong with it syntactically.
This gives you a lot of very cool runtime features that don't exist in C++... I hope that makes sense
You can pretty much do it all with C++ too if you like. There are perfectly well established extensions and libraries for reflection, AOP etc. And despite not being core language features, they are still nicer to look at than even the cleanest Objective C.