This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (103)
- # beginners (4)
- # boot (101)
- # cider (64)
- # clojure (126)
- # clojure-australia (1)
- # clojure-berlin (21)
- # clojure-china (1)
- # clojure-dev (11)
- # clojure-germany (13)
- # clojure-india (1)
- # clojure-italy (20)
- # clojure-japan (43)
- # clojure-poland (7)
- # clojure-russia (9)
- # clojure-spain (4)
- # clojure-uk (10)
- # clojurescript (152)
- # core-async (2)
- # css (51)
- # editors (25)
- # events (2)
- # instaparse (17)
- # jobs (1)
- # ldnclj (50)
- # om (7)
- # reactive (7)
- # reading-clojure (1)
- # reagent (1)
- # remote-jobs (1)
@martinklepsch: thx for the pointer, i joined the convo at https://gist.github.com/bhauman/5c50a25f28598d954eba
Btw, are they any thoughts on task parallelism? Don't need it but would be nice for sure :)
@martinklepsch: the problem with running tasks in parallel is not the mapping, it's the reducing
yeah, that was kind of what I was getting at with the question. Mapping is trivial but reduction not so much. Still probably doable with some proper constraints, right?
i.e. tasks executed in parallel are limited to a certain scope (read subdir) in the fileset
i think the conflict resolution part of the git model precludes any kind of automatic parallelization
I’m thinking just separating them might be fine in many cases, i.e. stylesheet + cljs compilation
Might be worthwhile to list the typical use cases for parallel tasks to see which of them need merging and which ones, like the case of stylesheet + cljs compilation, simply need to run to completion.
anyway the broccoli guys found that parallization isn't a significant improvement when you have pervasive and intelligent caching at the task level
the broccoli guys found that parallelization is most useful when work is being done more than once
I set that up after seeing it in another Slack and thought it’s a nice idea given that we often use words guys like guys, effectively (sometimes unconsciously) discriminating other genders, I think the auto messages are stupid though. They don’t give that kind of context.
alandipert: Normally I’ve always got a couple of favorites on my tweets. This one didn’t garner a single one. Sad.
Yeah I just wanted to share it here first as I know Micha and Martin would be interested
deraen: Thanks for letting us know about the Clojutre event. I submitted my proposal. What does "Vastauksesi on tallennettu” mean?
@juhoteperi: Berlin ✈️ Tampere sucks big time. Do you know how long does a train from Helsinki takes? (and what’s the price?)
@podviaznikov: There was a nice side-effect from using metadata for posts metadata, dates are now Date objects
@juhoteperi: do ClojurTRE tickets go fast usually or can I take a week or two to consider things?
@martinklepsch: They are going fast, but I'm sure there will be enough (we have quite large venue this year).
podviaznikov: I was going through the source code of perun, and I was wondering about the usage of unquote on regular function arguments, as in (io.perun.ttr/calculate-ttr ~metadata).