RemObjects Mercury vs. Small Basic vs. Unlambda vs. Visual Basic Comparison Chart

Mercury is an implementation of the BASIC programming language that is fully code-compatible with Microsoft Visual Basic.NET™, but takes it to the next level, and to new horizons. With Mercury, you will be able to build your existing VB.NET projects and leverage your Visual Basic™ language experience to write code for any modern target platform. You can mix Mercury code with any of the other five Elements languages in the same project if you like! The Mercury language will be deeply integrated into our development environments. Develop your projects in our smart yet lightweight IDEs, Water on Windows or Fire on Mac, with project templates, code completion, integrated debugging for all platforms, and many other advanced development features. Of course, Mercury will also integrate into Visual Studio™ 2017, 2019 and 2022. With Elements, all languages are created equal. Even within the same project, you can mix Mercury, C#, Swift, Java, Oxygene and Go.

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.