LambdaNative – Cross-platform mobile apps in Scheme
lambdanative.org
LambdaNative – Cross-platform mobile apps in Scheme
1–10 of 38 posts
Re: LambdaNative – Cross-platform mobile apps in Scheme
#2This looks awesome! I believe being able to express an entire app logic as data can be super powerful.
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. https://www.jasonette.com
Re: LambdaNative – Cross-platform mobile apps in Scheme
#3I 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.
Re: LambdaNative – Cross-platform mobile apps in Scheme
#4LOVE this project. My serious question is why wasn't this done in Racket as opposed to Scheme? Seems this would fit in Dr Racket wonderfully.
Re: LambdaNative – Cross-platform mobile apps in Scheme
#5Previous discussion, from about a year and a half ago: https://news.ycombinator.com/item?id=11192542
And a paper (2013) giving some details and explaining their motivations: http://ecem.ece.ubc.ca/%7Ecpetersen/lambdanative_icfp13.pdf
Re: LambdaNative – Cross-platform mobile apps in Scheme
#6LOVE this project. My serious question is why wasn't this done in Racket as opposed to Scheme? Seems this would fit in Dr Racket wonderfully.
Because racket isn't as easy to get running on smartphones as something that just compiles to C.
With gambitc you are already there.
Re: LambdaNative – Cross-platform mobile apps in Scheme
#7This 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.
Re: LambdaNative – Cross-platform mobile apps in Scheme
#8Previous discussion, from about a year and a half ago: https://news.ycombinator.com/item?id=11192542 And a paper (2013) giving some details and explaining their motivations: http://ecem.ece.ubc.ca/%7Ecpetersen/lambdanative_icfp13.pdf
The phone apps look like they are from 2013. That explains a lot.
Thanks for the links.
Re: LambdaNative – Cross-platform mobile apps in Scheme
#9It'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:https://software.intel.com/en-us/multi-os-engine
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 more readable, more maintainable, easier to understand, and far less error-prone, than programs written in dynamically typed languages.
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).
Re: LambdaNative – Cross-platform mobile apps in Scheme
#10I'd like to see someone code golf that calculator in javascript.