Yes! I saw the talk yesterday night, as well as Nada Amin's and Joe Armstrong's. Which is why I didn't get up in the morning :-)
Transducers are easier to understand than Rich's talk. What I mean by that is that Rich devotes a substantial part of the talk to explain the concepts of transducers in terms of types. Why does he do that if Clojure doesn't even have types? Because when you're talking at an elite conference like Strangeloop, where half of the audience come from academia, you are obliged to explain *any* CS concept in terms of types, because they won't have it any other way.
In practical tems, map, filter and all their friends are now not only applicable to collections, but any other *thing*. The other *things* could be a stream, an observable or a channel. These are the examples that Rich referred to, but the idea is that the *thing* is abstracted away from the operations.
I've been using transducers in the code for an upcoming talk on Om. In that talk, I plan to live code a prototype that retrieves and displays the RSVP'ed users for the current meetup. Here's how it look like:
https://github.com/danielsz/om-meetup/blob/master/dev/user.clj
The transducer is called results-xform and is used to process the results from a meetup API call.
It is defined independently, on its own, just a series of steps that can be reused anywhere if need be.
From my perspective, transducers promise to be useful with core.async channels, too.
--
Daniel Szmulewicz
http://about.me/daniel.szmulewicz
On 20/09/2014, at 13:48, Haim Ashkeanzi wrote:
> Hi all,
>
> I have a lot of articles on my reading list about transducers, but as you may know, work and kids leaves you much less time than you want to invest in educating yourself :)
>
> Then came along this talk (which is amazing that the video is released only a day after it was given) and now I have at least some idea what they are for :)
>
> https://www.youtube.com/watch?v=6mTbuzafcII
>
> Enjoy
>
> --
> Haim
>
> --
> You received this message because you are subscribed to the Google Groups "Clojure Israel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to clojure-israe...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Clojure Israel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to clojure-israe...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
And now for something completely different (sorry for hijacking the thread),Daniel congrats on om-mode. I’ll try it next time I’ll use om (which sadly might not be so soon :( ).
On Tue, Sep 23, 2014 at 11:05 PM, Daniel Szmulewicz <daniel.s...@gmail.com> wrote:Yes!I liked this too: http://elbenshira.com/blog/understanding-transducers/
On Sep 23, 2014, at 23:03, Tzach Livyatan <tzach.l...@gmail.com> wrote:I found the following usefulhttps://gist.github.com/ptaoussanis/e537bd8ffdc943bbbce7#file-transducers-clj
> To unsubscribe from this group and stop receiving emails from it, send an email to clojure-israel+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Clojure Israel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to clojure-israel+unsubscribe@googlegroups.com.
--Regards@TzachL--Regards@TzachL
--
You received this message because you are subscribed to the Google Groups "Clojure Israel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to clojure-israe...@googlegroups.com.