News for hackers. Stuff that matters.
Re:OpenBSD removes support for non-UTF8 locales by RexRollman on Friday August 14, 2015 @02:55PM (#10062074)
Personally, I wish everyone used the 24:00 clock. Maybe the military has messed me up, but I really prefer seeing something like 18:22 over 6:22pm. It just seems simplier.
Re:OpenBSD removes support for non-UTF8 locales by kazinator on Friday August 14, 2015 @08:46PM (#10063843)
The real beauty of the 24:00 clock is that it never actually shows that; at most 23:59. Then it goes to 0:00.

The 12:00 clock would be more respectable if it went from 0:00 (midnight/a.m.) to 11:59 a.m. then to 0:00 (noon/p.m.) and to 11:59 p.m. and never showed 12:00. (Let alone continuously flash such a thing as a demand that the time be set.)

Re:OpenBSD removes support for non-UTF8 locales by glandium on Friday August 14, 2015 @09:14PM (#10063912)
That's what 12:00 clocks display in Japan, fwiw, and it's much less confusing (because, really, jumping from 11:59am to 12:00pm is nonsensical for people not familiar with that quirk)
Re:OpenBSD removes support for non-UTF8 locales by blackbeard on Friday August 14, 2015 @03:08PM (#10062148)
Yes couldn't agree more with that.

Also dates in numeric order I.e. yyyy/mm/dd you know like all the other numbers we deal with not dd/mm/yyyy or the crazy mm/dd/yy.

Re:OpenBSD removes support for non-UTF8 locales by qznc on Friday August 14, 2015 @03:20PM (#10062243)
Use minus instead of slash and you have ISO 8601: yyyy-mm-dd
Re:OpenBSD removes support for non-UTF8 locales by krylon on Saturday August 15, 2015 @06:17AM (#10064962)
I had - I think - independently come up with this format for naming log files, and I was so very, very happy when I found out it is an ISO standard.

A little disappointed, too, because every single time I have a great idea like this, I find out that somebody else had it before me. But still.

Re:OpenBSD removes support for non-UTF8 locales by blackbeard on Friday August 14, 2015 @04:19PM (#10062665)
Sold.
Re:OpenBSD removes support for non-UTF8 locales by peterfirefly on Friday August 14, 2015 @04:33PM (#10062738)
8601 also gives you proper week numbering (which Europeans tend to like) + weeks start on Monday, after the weekend.
Re:OpenBSD removes support for non-UTF8 locales by jethro_tell on Friday August 14, 2015 @05:16PM (#10062990)
Well it's all the weekend. Saturday is the last end of the week and Sunday is the front end of the week.
Re:OpenBSD removes support for non-UTF8 locales by FullyFunctional on Friday August 14, 2015 @06:32PM (#10063391)
In the US perhaps, not in Europe
Re:OpenBSD removes support for non-UTF8 locales by robin_reala on Friday August 14, 2015 @07:26PM (#10063602)
In the UK too traditionally, although that’s changing (by convention).
Re:OpenBSD removes support for non-UTF8 locales by kazinator on Friday August 14, 2015 @09:05PM (#10063889)
Yet, in America, people say things like "do you have plans for the weekend?" Or, "What did you do last weekend?"

Nobody ever says, "Do you have plans for the upcoming two days which, respectively, constitute the end of this week and the start of the next one?"

So, Americans and Brits are inconsistent. They have "the weekend" which is a block of two days when salaried people with regular working hours don't work; and they have Sunday as not the week end, but rather the beginning; or the "front end" of the next week. Which means that the two days cannot be the weekend; they are two different ends of two different weeks.

> that's changing (by convention)

It's changing because people have to confront the above reasoning and realize that a week beginning in the middle of something that they have been calling "the weekend" for decades is silly.

Re:OpenBSD removes support for non-UTF8 locales by vacri on Saturday August 15, 2015 @12:23AM (#10064305)
Neither does anybody say "What are you doing for the holidays constituted of Christmas Day and selected other days around it?"
Re:OpenBSD removes support for non-UTF8 locales by ciupicri on Saturday August 15, 2015 @08:20AM (#10065193)
Christmas has 3 days.
Re:OpenBSD removes support for non-UTF8 locales by baudehlo on Friday August 14, 2015 @06:06PM (#10063282)
In some countries the weekend isn't Saturday and Sunday though. So the start of the week is kind of arbitrary.
Re:OpenBSD removes support for non-UTF8 locales by saljam on Friday August 14, 2015 @11:13PM (#10064171)
Saudi Arabia used to have it's weekend on Thursday & Friday. Recently they've switched to Friday & Saturday.
Re:OpenBSD removes support for non-UTF8 locales by caf on Saturday August 15, 2015 @08:16AM (#10065184)
I believe in my entire life I've encountered exactly one situation in which the day that is defined as the first day of the week actually made a difference to anything: my kids' swim school schedule, where Week N of the term runs from Sunday through to the following Saturday inclusive.

Since the working week (and the school week) here starts on Monday regardless of whether Sunday or Monday is regarded as the first day of the week, it seems to have always been a distinction without a difference to me.

Re:OpenBSD removes support for non-UTF8 locales by Asbostos on Saturday August 15, 2015 @01:21AM (#10064418)
Yes. Putting the year first and with 4 digits is the only safe way because, afaik, nobody anywhere uses yyyy/dd/mm. It's nice that it's also in order of significance but the main advantage is unambiguousness.

You'd think people would have learnt from Y2K but somehow we still see 2-digit years which make dates like 03/04/05 impossible to even guess at. It's slightly better since 2012 where a 2-digit year can't also be a month, but we'll have to wait till 2032 for 2-digit years to unambiguously mean year.

This is an area where I believe localization makes things worse, not better. If every website showed dates with the year first, people would easily understand, regardless of whatever silly local convention they have. As it is, whenever I see a ##/##/## date, I have to think about what the website might be trying to do (do they know what country I'm from? What country I'm in now? Are they using their own local convention?) and what possible dates it might mean. "I think that happened around August, so 08/10/14 is probably not the 8th of October." Localized dates just make no sense at all on the internet.

Re:OpenBSD removes support for non-UTF8 locales by hyperion2010 on Friday August 14, 2015 @11:28PM (#10064201)
I cannot tell you the number of times in my life that a 12 hour clock has lead to a _major_ fuckup. I run all my personal clocks on 24hr to prevent said fuckups, but somehow I still feel weird telling people a meeting is at 15:00 in an email.
Re:OpenBSD removes support for non-UTF8 locales by roghummal on Saturday August 15, 2015 @05:53AM (#10064902)
>but somehow I still feel weird telling people a meeting is at 15:00 in an email.

It feels weird because you think people will think it's weird. You're probably right.

Personally I use a 24-hour representation and convert it to 12 when communicating with others.

11:59AM -> 12:00PM, 11:59PM -> 12:00AM caused me mental discomfort for a long time. A 24-hour clock made a lot more sense, but it doesn't seem like most other people have a problem with 12.

They'd rather you used "normal" time. If you want to fight that battle go for it. I believe you're right.

Next: Date format!

Re:OpenBSD removes support for non-UTF8 locales by krylon on Saturday August 15, 2015 @05:00AM (#10064781)
I have not served in the military (we still had the draft in Germany when I finished school, but I was a conscientious objector), but I greatly prefer the 24-hour time format as well.

Maybe digital clocks/watches have influenced this preference, but I still think it is a good idea, because it is unambiguous.

Re:OpenBSD removes support for non-UTF8 locales by cpeterso on Saturday August 15, 2015 @03:50AM (#10064675)
Plus people format 12 hour times inconsistently:

  6:00pm
  6:00PM
  6:00 PM
  6:00 P.M.
  6PM
  or just 6:00
Re:OpenBSD removes support for non-UTF8 locales by ape4 on Saturday August 15, 2015 @11:48AM (#10065681)
There is something to be said for the french style 18h00. So when you see the "h" you know its 24-hour time. With the colon you aren't sure if its 12 or 24 hour time.