BoxLang vs. Java vs. Unlambda vs. metaphactory Comparison Chart

BoxLang is a modern, dynamically and loosely typed scripting language for the Java Virtual Machine (JVM) that supports Object-Oriented (OO) and Functional Programming (FP) constructs. It can be deployed on multiple platforms and all operating systems, web servers, Java application servers, AWS Lambda, WebAssembly, and more. BoxLang combines many features from different programming languages to provide developers with a modern, fluent, and expressive syntax. BoxLang has been designed to be a highly modular and dynamic language that takes advantage of all the modern features of the JVM. It is dynamically typed, which means there's no need to declare types. It can perform type inference, auto-casting, and promotions between different types. The language adjusts to its deployed runtime and can add, remove, or modify methods and properties at runtime.

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.