3 ms·
I and many other experienced people on #clojure@freenode looked at this. Heard comments such as: “Huh.” “I can't believe -> and ->> are being demonize
by KirinDave 16y ago
I and many other experienced people on #clojure@freenode looked at this.
Heard comments such as:
“Huh.”
“I can't believe -> and ->> are being demonized now.”
”I think if you're calling things rules you should be somewhat careful about how you phrase them...”
“Someone is wrong on the internet.”
- alnayyir 16y agoSounds about right. Since you're apparently familiar with both Clojure and Erlang, what are your feelings regarding the concurrency model in each?
- KirinDave 16y agoThey are both good for different things. :) The clojure model means state is easy to move around. This is awesome. The Erlang model makes the server-like nature of each component very explicit, which can significantly reduce the complexity of some types of systems.
- alnayyir 16y agoCool, thanks for your thoughts. I always felt like Clojure was attempting a permissive system, whereas Erlang really is pretty up-front about the environment it's designed to work in. I keep meaning to fiddle with Reia but never got around to it.
- sqrt17 16y agoThe real reason why you want ->> can be seen in the code example for rule #7: instead of mapping the result of partitioning, it (wrongly) reuses a (i.e., the original list). If bugs result in irregularity, then making regularity explicit (by using ->> or other macros/higher-order functions) can be a good thing.
- KirinDave 16y agoGood catch! That's a very good point, and a very hard bug to see when you "get lazy" and use a, b, c as step names.