[abhilash0505]

If one had done Ruby programming in its early days, he/she would come across an epiphany. I tried swift and the best part was the similarity to Ruby and the ease of use. Plus, loads of built in lib functions just make development easier. Added to that, the amazing lldb support for Swift is wonderful.

But what's not so great?? The fact that there will be two languages with greatly different syntaxes in the same file. It would just remind you of the initial days of iOS programmer's surge when many realised that Objective C file could also contain C code.

Some find this mixture of languages fun, and some would probably not feel the same.

If the acceptance is the same as it was for Objective C, maybe this is the Objective C 2.0 successor.

[AlexanderDhoore]

This IS the Objective-C 2.0 successor. Apple does not do acceptance tests. (This is a good thing, if you ask me.)

[gbrhaz]

The languages won't be in the same file. They can be in the same project, of course, but at least they'll be separated. It means you can write a class in one language and use it in the other language, without having to worry about it breaking.