Hacker News Reader

Comment by curun1r | Hacker News Reader

And it's because of dumb non-programmers that we have 12am immediately following 11pm. If we were to, instead, recognize the beginning/middle of the day as 0, the am/pm transitions would be sensible.

Starting at 0 is almost always correct, teaching people to start counting at 1 isn't. Why do we continually come up with convoluted workarounds simply because we educate children incorrectly?

View on HN

I believe that hours going up to 12 instead of going 0 .. 11 is because you can't quite hear a bell strike zero times, no?

Although that's kind of a clever response, most bells have a chime to alert you to the hour change so it would just be the chime without the counted bell strikes. Better yet, since 0 would always be the start of a new day, make the strikes do some kind of awesome song.

Wat? There are 24 hours in a day 1-24 or 0-23, pick your poison. But 100% Fuck halfday, 1-12 bullshit.

P.S. Also fuckoff non-UTC time.

Fuck hours. There's only 1440 minutes a day. No time for hour conversions.

I wish we could all schedule things on UTC time. I've been part of 10 person meetings across 4 time zones and scheduling sucks. Inevitably someone assumes a meeting is scheduled in their local time.

You don't have to be in UTC, but having your clock set to 24 hours still makes it a lot easier.

After a year of daily meetings with people on the east coast (of the US), London, Hamberg, and Brasilia from the west coast of the US I just moved to 24 hours and found it much easier to mentally calculate everyone's respective times- as long as I could keep the offsets squared away.

Screw daylight savings.

It's even worse when you don't observe DST but basically everyone else does.

I can't even keep the offsets squared away since they shift a couple times a year.

Reply on news.ycombinator.com