CFML vs Xtend

Get a web app up and running fast with stuff built right in to CFML! Frameworks make it even faster but lengthen the learning curve.

Newcomers can use an html-like syntax to query a database. Advanced developers can use a scripted syntax to execute stored procedures.

There are multiple engine implementations available including Adobe ColdFusion, Lucee, New Atlanta BlueDragon, Railo, and Open BlueDragon among others.

ColdFusion can quickly interact with PDFs , Spreadsheets to read/manipulate the data. There are a lot of built in functions to manipulate images quickly.

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.

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.

Because Xtend relies heavily on JDK and Android classes, it runs just as fast as native Java code.

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.

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.)

Uses functional features ,which are very concise and idiomatic. Plus it has annotations, which cuts down on the Java boilerplate.

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.