Objective-C vs Xtend
When comparing Objective-C vs Xtend, the Slant community recommends Xtend for most people. In the question“What is the best programming language to learn first?” Xtend is ranked 68th while Objective-C is ranked 74th. The most important reason people chose Xtend is:
Lambdas are written like Smalltalk's blocks. If it's the last argument, it can go after the parentheses like Ruby's blocks. Parentheses on method calls are optional.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Well Documented
Objective-C's documentation exists on Apple's website, and explains language features in detail.
Pro Develop Apple applications
Similar to C# and Java, but used to develop native applications for Apple hardware.
Pro Objective-C supports an open style of dynamic binding
A style that can accommodate a simple architecture for interactive user interfaces.
Pro Ruby-like syntactic conveniences
Lambdas are written like Smalltalk's blocks. If it's the last argument, it can go after the parentheses like Ruby's blocks. Parentheses on method calls are optional.
Pro Type inference
It uses Java's static type system, but you don't have to declare the type of everything all the time, since the Xtend compiler can usually figure it out. This also dramatically cuts down on Java's infamous verbosity.
Pro Code runs just as fast as Java
Because Xtend relies heavily on JDK and Android classes, it runs just as fast as native Java code.
Pro Easy to switch back to Java
Xtend is a low-risk option. Because it compiles to human-readable Java, if you decide you don't like it for your project, you can just switch back to Java without losing your work.
Pro Extend even library classes with new methods
This is where it gets its name. You can open classes and add new methods, kind of like Ruby. (Of course this has to be compiled to Java, so really it lives in a kind of helper class.)
Pro Succint
Uses functional features ,which are very concise and idiomatic. Plus it has annotations, which cuts down on the Java boilerplate.
Pro Better defaults than Java
Methods are public if you don't specify, and fields are private. Locals declared with val
in Xtend are final
in Java. This dramatically cuts down on Java's infamous verbosity.
Cons
Con Odd Syntax
Objective C's syntax is very alien to other languages. Learning Objective-C first will fail to expose you to a syntax style that would be relatively familiar in almost any other language.
Con Might as well learn Swift
Swift works almost anywhere Objective C does, and it was designed to replace Objective C.
Con One of the biggest mistakes ever.
It was meant to be one of the C-style languages, but has such bad syntax design it actually is the odd duck.
Con Apple-centric and obsolete
Con Tied into Apple's eco-system.
Con More Technical
To be able to do basic tasks in Objective-C requires a strong understanding of programming.
Con Requires Understanding of C-language.
Objective-C is built on top of C, and as such, requires at least a basic understanding of how to program in C.
Con Difficult to configure in Android Studio
Con Slower compilation
Unlike most JVM languages, Xtend compiles to Java rather than directly to JVM bytecode. So you have to compile everything four times for Android: from Xtend to Java, from Java to JVM bytecode (.class files), from .class to .dex bytecode, and then AOT compilation from .dex to native ARM upon installation. This can really slow down development and testing vs a more interactive language like Clojure.