this post was submitted on 01 May 2025
1077 points (97.0% liked)

Comic Strips

16329 readers
1751 users here now

Comic Strips is a community for those who love comic stories.

The rules are simple:

Web of links

founded 2 years ago
MODERATORS
top 50 comments
sorted by: hot top controversial new old
[–] ILaughBecauseFunny@feddit.dk 13 points 1 day ago

Issue: there are 27 different ways of writing a date.

Engineers: We most make a common standard that is unambiguous, easy to understand and can replace all of these.

Issue: there are 28 different ways of writing a date.

Joke aside, I really think the iso standard for dates is the superior one!

[–] callyral@pawb.social 13 points 1 day ago

2013-02-27 = 1984

[–] whotookkarl@lemmy.world 20 points 1 day ago

2013-02-27 is a weird way of writing 1361923200

[–] Benchamoneh@lemmy.dbzer0.com 9 points 1 day ago

I agree with the ISO approach, but unfortunately without mainstream adoption in a majority of countries it's just another standard.

[–] arc@lemm.ee 30 points 1 day ago (7 children)

The sane way of dealing with it is to use UTC everywhere internally and push local time and local formatting up to the user facing bits. And if you move time around as a string (e.g. JSON) then use ISO 8601 since most languages have time / cron APIs that can process it. Often doesn't happen that way though...

[–] expr@programming.dev 7 points 1 day ago

Generally yes, that's the way to do it, but there are plenty of times where you need to recreate the time zone something was created for, which means additionally storing the time zone information.

[–] nBodyProblem@lemmy.world 1 points 1 day ago (1 children)

The BEST way is to use the number of seconds after the J2000 epoch (The Gregorian date January 1, 2000, at 12:00 Terrestrial Time)

[–] arc@lemm.ee 1 points 10 hours ago

ISO 8601 goes from 1582 (Julian calendar adoption) but can go even further with agreement about intention and goes down beyond the millisecond. Not sure why I want an integer from the year 2000 which only represents seconds.

load more comments (5 replies)
[–] WoodScientist@sh.itjust.works 45 points 1 day ago (1 children)

I propose that we amend the ISO to require the days of the week be named after their etymological roots in that language.

English Days of the Week:
Day of the Sun
Day of the Moon
Day of Týr
Day of Odin
Day of Thor
Day of Frēa
Day of Saturn

Imagine dating a meeting, "Day of Odin, May 7, 2025." Imagine a store receipt that says, "Day of Thor, June 5, 2025." Imagine telling a friend, "July 4th falls on a Day of Frēa this year!"

THIS IS WHAT WE COULD HAVE. THIS IS WHAT WE HAVE LOST. THIS IS WHAT WAS STOLEN FROM US.

We could bring it back. We could make this the norm. We could make this real. We could summon this bit of ancient magic back into our world. Let's remember what we actually named these days for! BRING BACK THE DAY OF THOR!

[–] fibojoly@sh.itjust.works 7 points 1 day ago

That would work better if Latin wasn't there before English. Mars Victor!

[–] starman2112@sh.itjust.works 67 points 2 days ago (2 children)

I am a big fan of iso 8601, I just wish it was possible to write more dates than February 27th, 2013 with it

load more comments (2 replies)
[–] CidVicious@sh.itjust.works 172 points 2 days ago (4 children)

Rich is right, since this is the date format that sorts correctly in filenames.

[–] compostgoblin@slrpnk.net 96 points 2 days ago (1 children)

And it is easily extensible to YYYY-MM-DDThh:mm:ss to include the time of day

[–] blazeknave@lemmy.world 13 points 2 days ago (2 children)
load more comments (2 replies)
[–] brsrklf@jlai.lu 41 points 2 days ago (9 children)

Won't be true after 9999-12-31, however.

[–] otacon239@lemmy.world 107 points 2 days ago (1 children)
[–] Brunbrun6766@lemmy.world 35 points 2 days ago (2 children)

Can't wait for the Y40k bug, when Tyranids begin to infect our brains.

load more comments (2 replies)
[–] GreyEyedGhost@lemmy.ca 14 points 2 days ago

If I, my software, or my data last this long, I will have nearly 8000 years to resolve it. Which is to say, the year 9998 is going to get busy.

load more comments (7 replies)
[–] waigl@lemmy.world 34 points 2 days ago* (last edited 2 days ago) (1 children)

Who's Rich? Did you mean Randall?

[–] CidVicious@sh.itjust.works 27 points 2 days ago (3 children)

...dammit, the only comics I read are XKCD and OOTS and I done fucked up.

load more comments (3 replies)
load more comments (1 replies)
[–] driving_crooner@lemmy.eco.br 5 points 1 day ago

In the last company I work for, the department was created from zero, and my boss just let me take all the technical decisions so from the begging everything was wrote in ISO-8601. When I left it was just the way it was, if you try to use any other date format anywhere something is going to give you an error.

[–] ChaoticNeutralCzech@feddit.org 22 points 1 day ago (2 children)

Where I live, "DD. MM. YYYY" is the standard but some old tombstones use

first two digits of year, then a "proper" (horizontal-bar) fraction of DD/MM, then second two digits of year

[–] De_Narm@lemmy.world 15 points 1 day ago (1 children)

Do you know why one would ever do that? 20(02/05)25 feels like the "Don't Dead Open Inside" of dates.

[–] ameancow@lemmy.world 8 points 1 day ago

Which is exactly why they're used on tombstones. See, the world makes sense after all!

load more comments (1 replies)

This is the way.

[–] elDalvini@discuss.tchncs.de 87 points 2 days ago (8 children)

Alt text:

ISO 8601 was published on 06/05/88 and most recently amended on 12/01/04.

load more comments (8 replies)
[–] vga@sopuli.xyz 18 points 2 days ago* (last edited 2 days ago)

ISO 8601 allows all kinds of crazy time stamps. RFC 3339 is much nicer and simpler, and the sweet spot is at the intersection of ISO 8601 and RFC 3339.

Then again, ISO 8601 contains some nice things that RFC 3339 does not, like ranges and durations, recurrences...

https://ijmacd.github.io/rfc3339-iso8601/

[–] thesmokingman@programming.dev 48 points 2 days ago (23 children)

There are several people in the comments saying they have to use 27 Feb 2013 because they work with people all over the world. I’m really confused - what does that solve that 2013-02-13 does not? I know that not every language spells months the English way so “Dec” or “May” aren’t universal. Is there some country that regularly puts year day month that would break using ISO 8601 or RFC 3339?

[–] Saleh@feddit.org 38 points 2 days ago (5 children)

I think learning all abbreviations for different months in different languages is more complicated than just learning that the time is sorted from largest to smallest unit.

load more comments (5 replies)
load more comments (22 replies)
[–] essteeyou@lemmy.world 32 points 2 days ago (1 children)

My goodness, some of the comments in here must come from people who thought that those writing the standard were morons who did no research.

load more comments (1 replies)
[–] abbadon420@lemm.ee 2 points 1 day ago (1 children)

@m_f@discuss.online this might be applicable to the farside as well

[–] m_f@discuss.online 1 points 1 day ago (1 children)

Do you mean the post titles? I've been using the same format as was used since before I took over posting, but if people want ISO format that works for me

[–] abbadon420@lemm.ee 2 points 22 hours ago

I'm all for ISO format. I can't imagine anyone having objections.

[–] ripcord@lemmy.world 17 points 2 days ago (2 children)
load more comments (2 replies)
load more comments
view more: next ›