-
-
Replying to @peterseibel
@peterseibel@argyris but Easter comes at approximately the same time (never June). I don't think they meant the same date.2 replies 0 retweets 0 likes -
Replying to @posco
@posco@peterseibel yeah though it can be anytime between March and May AFAIK1 reply 0 retweets 0 likes -
Replying to @argyris
@argyris@peterseibel okay. Maybe that delta is wide enough to disqualify from "same time each year". But the vast majority are ~ same time.2 replies 0 retweets 0 likes -
Replying to @posco
@posco@peterseibel I think that there's a few other christian ones that move around. Most god related things are messy1 reply 0 retweets 0 likes -
Replying to @argyris
@argyris@posco@peterseibel not messy, just an extra constraint: each date should be roughly fixed w.r.t both the solar *and* lunar cycles.2 replies 0 retweets 0 likes -
Replying to @avibryant
@argyris@posco@peterseibel *you* try designing a calendar that satisfies that.1 reply 0 retweets 2 likes -
Replying to @avibryant
@avibryant@argyris@peterseibel what if we move the moon and slow down the earth to make EXACTLY 365 days/year and EXACTLY 12 months/year.2 replies 0 retweets 2 likes -
Replying to @posco
@posco@argyris@peterseibel 13 x 28 = 364 is simpler, surely? While you’re messing with orbits.2 replies 0 retweets 3 likes -
Replying to @avibryant
@avibryant@argyris@peterseibel yes, that's very compelling. But 12 has so many divisors and 13 none. Tough call.1 reply 0 retweets 1 like
@posco @argyris @peterseibel which reminds me: groupBy(_.midnightTimestamp).withReducers(96) leads to horrible skew. #hashCode
-
-
Replying to @avibryant
@avibryant@posco@peterseibel this also reminds me that you were insisting on using pacific time for our hadoop rollups :)1 reply 0 retweets 2 likes -
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.