It's a bit inaccurate of them to present the results of a 17-year old paper (published in 2000), as empirical evidence that development time in Scheme is shorter. These days there are plethora of language choices on the JVM, and if I were devloping a multi-platform app today, I would personally choose Kotlin along with the Intel Multi-OS Engine:<a href="https://software.intel.com/en-us/multi-os-engine" rel="nofollow">https://software.intel.com/en-us/multi-os-engine</a><p>Part of my motivation to prefer Kotlin over Clojure (the most popular LISP on the JVM langauge?) is that I am a huge proponent of static typing. Large programs written in statically typed languages are orders of magnitute <i>more readable</i>, more maintainable, easier to understand, and far less error-prone, than programs written in dynamically typed languages.<p>The recent surge in popularity of dynamically typed languages like JavaScript, Python, Ruby, etc, had been a source of horror and frustration to me. It feels like a huge segment industry is throwing away decades of advancement made in programming language research, and instead of moving to languages with more advanced type systems, they're abandoning sound typing altogether (shudder).
Gambit is a fantastic scheme system. The performance you get from it exceeds even SBCL in my limited use cases. Additionally, Gerbil Scheme (<a href="http://cons.io" rel="nofollow">http://cons.io</a>), built on Gambit, has expanded syntax like racket's #lang features for dsls. Several packages have also been create for it for most of the things I need.
A recent example of cross-platform app/game made with LambdaNative: <a href="https://www.reddit.com/r/scheme/comments/6hng3q/i_developed_a_medium_sized_cross_platform/" rel="nofollow">https://www.reddit.com/r/scheme/comments/6hng3q/i_developed_...</a>
This project blew me away. I always thought Scheme was just interpreters and toy programs. Hope this succeeds in making scheme popular. Scheme and Lisps in general way too underrated.
Previous discussion, from about a year and a half ago: <a href="https://news.ycombinator.com/item?id=11192542" rel="nofollow">https://news.ycombinator.com/item?id=11192542</a><p>And a paper (2013) giving some details and explaining their motivations: <a href="http://ecem.ece.ubc.ca/%7Ecpetersen/lambdanative_icfp13.pdf" rel="nofollow">http://ecem.ece.ubc.ca/%7Ecpetersen/lambdanative_icfp13.pdf</a>
This looks awesome! I believe being able to express an entire app logic as data can be super powerful.<p>BTW shameless plug: If you're interested in this type of ideas, please also check out Jasonette (an open source project I'm working on) Just like this project uses "list" to describe an app, Jasonette uses JSON to describe an app. <a href="https://www.jasonette.com" rel="nofollow">https://www.jasonette.com</a>
I love it! This is awesome idea, now that I see it, I wonder why wouldn't Google just use it, if Apple will not, this makes total sense for mobile apps. Pair it with high performance native api, it can be winning ticket.