Deborah Pickett6d ago
I have a date arithmetic bug for you.
Show threadDeborah Pickett6d ago
Oh god someone is going to explain to me why this isn’t a bug, aren’t they?
Show threadI love this, so I6d ago
@futzle leap years were a mistake
Show threadlick here for more info6d ago

@jpm think he just posted it about 8 hours short of 10 years apart.

And to be fair, the post does say "today", not "now"!

sorry for doing the thing you said we would do @futzle 

Show threadDeborah Pickett
@virtulis @jpm Indeed, it emerges from confusion of date arithmetic with datetime arithmetic. Also time zones are a factor in date arithmetic.
Mar 16 at 8:07amWeb
Show threadI love this, so I6d ago
@futzle @virtulis we would not have this issue if everyone used hyperlocal solar noon as their display time
Show threadMagnus Ahltorp6d ago
@futzle @virtulis @jpm Time zones should not be a factor when calculating how long ago something is, should they? 1 hour is 1 hour, even if we are in different time zones. I'm guessing the HCI problem here is that "year" is not a useful unit to truncate the decimal part of.
Show threadDeborah Pickett6d ago
@ahltorp @virtulis @jpm I said time zones are a factor in date arithmetic, not in datetime arithmetic. This moment now is 17 March for me and probably 16 March for you. If we do date arithmetic on a now() timestamp, you and I will get different results.