News for hackers. Stuff that matters.
Re:Again on 0-based vs. 1-based indexing by vbarrielle on Wednesday January 20, 2021 @04:05AM (#25844208)
> Our time counting is 1-based.

Not in every part in the world. Here in France, we use 24h time, and midnight is 00:00. Very convenient.

Re:Again on 0-based vs. 1-based indexing by OJFord on Wednesday January 20, 2021 @04:16AM (#25844279)
I'm not French, but your comment just made me 'realise' that people who use 12h have the largest numbers when we on 24h have the smallest, almost like the 'start' is one o'clock. Weird.

Same :00 start happens with minutes on 12h though of course.

I think GP didn't mean to talk about time, has a point regarding months as I replied elsewhere. We represent the months numerically as 1-12, and I have recently found that annoying to work with.

Re:Again on 0-based vs. 1-based indexing by linknoid on Wednesday January 20, 2021 @08:49AM (#25846379)
12:00 should actually be 0:00 on the 12 hour clock, it belongs to the next 12 hour period. 11:59 PM is yesterday, 12:00 AM is one minute later, and falls on today. Same with noon, 12:00 PM comes one minute after 11:59 AM. When I see 12:00, I automatically convert that to 0:00, otherwise AM/PM doesn't make sense.
Re:Again on 0-based vs. 1-based indexing by vbarrielle on Wednesday January 20, 2021 @04:22AM (#25844327)
Indeed, months are 1 based, but it's never been a problem to eg compute which month it will be, say 9 months later: just sum and subtract 12, no need for a real modulo computation. It's probable I've never found it annoying because I don't need to perform this computation with more than 12 months.
Re:Again on 0-based vs. 1-based indexing by IlliOnato on Wednesday January 20, 2021 @07:07PM (#25853618)
Yeah, this is most familiar to me too. Still, I'd argue it's 1-based. 00:00 is a point in time, but the first second is between 00:00:00 and 00:00:01, and it's "00:00:01" when it has elapsed.

No?