CoreIDE vs. Grails vs. Java vs. Unlambda Comparison Chart

A powerful Groovy-based web application framework for the JVM built on top of Spring Boot. Convention-over-configuration, sensible defaults, opinionated APIs, and the Groovy language combine to make the Grails® framework easy to learn for Java developers. The Grails framework is built on top of Spring Boot and leverages Spring Boot's time-saving features, such as Spring-powered dependency injection. The Grails framework seamlessly and transparently integrates and interoperates with Java, the JVM, and existing Java EE containers. Apache Groovy is a language for the Java platform designed to enhance developers' productivity. It is an optionally-typed and dynamic language but with static-typing and static compilation capabilities. The Grails framework seamlessly integrates with GORM, a data access toolkit that provides a rich set of APIs for accessing relational and non-relational data. GORM also includes implementations for Hibernate (SQL), MongoDB, Cassandra, and Neo4j.

Unlambda is a programming language. Nothing remarkable there. The originality of Unlambda is that it stands as the unexpected intersection of two marginal families of languages. Functional programming languages, of which the canonical representative is Scheme (a Lisp dialect). This means that the basic object manipulated by the language (and indeed the only one as far as Unlambda is concerned) is the function. Rather, Unlambda uses a functional approach to programming: the only form of objects it manipulates are functions. Each function takes a function as an argument and returns a function. Apart from a binary “apply” operation, Unlambda provides several built-in functions (the most important ones being the K and S combinators). User-defined functions can be created, but not saved or named, because Unlambda does not have any variables.