On Sunday, December 7, 2014 5:37:20 PM UTC+11, James MacAulay wrote: > > Along those lines, I had previously explored using core.async with JS > promises [1] and "async futures" [2]. >
Interesting, I think this here goes along the same lines: https://github.com/logaan/promise-stream > I decided to read Evan Czaplicki's 2012 thesis on Elm to understand that > different perspective better, and the more I understood it the more > compelling I found that approach. I had a very similar experience with the > paper as Eric Normand recently described [3], and that Concurrent ML code > was just begging to be ported to core.async :) > So your motivations seem all good but I have a gut feeling that by embracing Elm you are painting yourself in a corner. As in, it seems neat but eventually you hit some brick wall that can't be overcome and you realize you have to go back and take off into yet another direction. I have refrained from going down the Elm path for that reason. This particular obstacle here may well turn out to be the brick wall that can't be overcome: > The fact that Elm's signal graphs are static does present some challenges > and ... > People are still figuring out how best to structure larger applications in > Elm > Regarding "clean code": > At its best, Elm code is some of the clearest code I've seen, with almost > zero "baggage" (read: incidental complexity). > I'm wondering how much of that cleanliness stems from the code being toy-sized, not from being FRP. > Furthermore, Zelkova brings its own advantages by being embedded in and > implemented entirely in Clojure/ClojureScript. > Agreed on Clojure, I can't wait for FRP to arrive in Clojure. Not the least b/c the Haskell community that Elm comes from leans towards academia and theories whereas the Clojure community is more show-me-the-money. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
