On Sunday, 7 December 2014 19:41:58 UTC-5, nchurch wrote:
>
> Did you ever look into Hoplon/Javelin? Haven't heard much about it on
> this group recently, and curious why
>
As it happens, Alan Dipert gave a great remote presentation on Hoplon to my
local Clojure user group (Clojure Toronto)
Did you ever look into Hoplon/Javelin? Haven't heard much about it on this
group recently, and curious why
On Saturday, December 6, 2014 10:37:20 PM UTC-8, James MacAulay wrote:
>
> What prompted me to write Zelkova?
>
> The short answer is curiosity and gut feeling. The long answer:
>
> I c
On Sunday, 7 December 2014 02:01:33 UTC-5, eric wrote:
>
> Interesting, I think this here goes along the same lines:
> https://github.com/logaan/promise-stream
>
>
Cool, I'll check that out. Hadn't seen that one before. I was also happy to
see Rich Hickey talking about the upcoming Promise Cha
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 decid
What prompted me to write Zelkova?
The short answer is curiosity and gut feeling. The long answer:
I consider core.async (and CSP in general) to be an excellent low-level
abstraction for coordinating concurrency, but I feel like it relies way too
much on mutating operations for me to want to us
i guess "big projects" at the bottom of
http://elm-lang.org/Examples.elm
--
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 w
Any "real things" that have been achieved that you'd want to highlight? I'd
be interested in porting them to Clojure, possibly using Zelkova, as an
exercise in FRP coding.
On Sunday, December 7, 2014 12:29:19 PM UTC+11, raould wrote:
>
> > From what I understand it's conceptually not ready for a
> From what I understand it's conceptually not ready for anything other
> than toy problems yet. Like Elm's restriction on static flow graphs. It's
> like programming without 1st class functions, you don't get very far.
I am not an Elm user, but I am on the mailing list :-) and I see real
things
Hi,
May I ask what prompted you to write this? A coding exercise or some
real-world need? I'm asking because I've been keeping an eye on FRP for a
while. From what I understand it's conceptually not ready for anything
other than toy problems yet. Like Elm's restriction on static flow graphs.
I
I've just published an FRP library based on Elm[1]:
https://github.com/jamesmacaulay/zelkova
Here's what the app code looks like:
https://github.com/jamesmacaulay/zelkova/blob/4b06c49678e11e3af7b1eda7a18929a512f7753d/examples/mario/src/mario/core.cljs#L118-L133
Right now Zelkova includes ports
10 matches
Mail list logo
