It does feel like a tradeoff that was a bit too harsh. As the post shows, you can work around it... but at the end of the day my code ends up with a ton of (nth 0) and very few (first) calls. It feels a bit ugly.. and it doesn't feel "idiomatic" as in how you learn Clojure from a textbook. Some more discussion of it here: https://clojureverse.org/t/what-do-beginners-struggle-with/5...
I find the threaded stuff much easier to follow. Maybe it's mostly visual and familiarity
Comments
It seems like an intentional design choice. didibus sorta explained it to me: https://news.ycombinator.com/item?id=28406315
It does feel like a tradeoff that was a bit too harsh. As the post shows, you can work around it... but at the end of the day my code ends up with a ton of (nth 0) and very few (first) calls. It feels a bit ugly.. and it doesn't feel "idiomatic" as in how you learn Clojure from a textbook. Some more discussion of it here: https://clojureverse.org/t/what-do-beginners-struggle-with/5...
I find the threaded stuff much easier to follow. Maybe it's mostly visual and familiarity
And as an interesting extra: https://clojureverse.org/t/x-x-auto-transducifying-thread-ma...