▲ 657 ▼ The perfect date (lemmy.world) submitted 4 days ago by PopcornPrincess@lemmy.world to c/lemmyshitpost@lemmy.world 239 comments fedilink hide all child comments
[–] red_tomato@lemmy.world 319 points 4 days ago (35 children) ISO 8601 permalink fedilink source hideshow 42 child comments replies: [–] 7EP6vuI@feddit.org 200 points 4 days ago (7 children) ISO 8601 YYYY-MM-DD permalink fedilink source parent hideshow 13 child comments replies: [–] jlow@slrpnk.net 46 points 4 days ago 👆 permalink fedilink source parent [–] GreyEyedGhost@piefed.ca 16 points 3 days ago (2 children) RFC 3339 FTW! Open source, and no ambiguous options grandfathered in. permalink fedilink source parent hideshow 4 child comments replies: [–] bss03@infosec.pub 5 points 3 days ago Was looking for this. Yes. Whenever possible, dates should be specified in a format that is BOTH RFC 3339 and ISO 8601. I'd say both have their quirks, but the intersection of the grammars is machine-parseable and human-readable without (much) legacy baggage or (much) experimental / reserved-for-future-use noise. permalink fedilink source parent [–] The_Decryptor@aussie.zone 2 points 3 days ago Though the way it specifies raw UTC times is odd (8601 uses Z, 3339 uses -00:00), that got changed with RFC 9557 to align with 8601. It also supports "zoned date times", where instead of just using the UTC offset, you can also include a timezone identifier, e.g. 2020-01-01T00:00+01:00[Europe/Paris]. Useful if you're doing calculations on dates but can be ignored otherwise. permalink fedilink source parent [–] plasma8726@lemmy.today 13 points 3 days ago This is the only way to date. permalink fedilink source parent [–] CanadianCarl@sh.itjust.works 1 point 2 days ago ISO week date permalink fedilink source parent [–] Iusedtobeanalien@lemmy.world 3 points 3 days ago (1 child) No need for dashes permalink fedilink source parent hideshow 2 child comments replies: [–] sem@piefed.blahaj.zone 4 points 3 days ago Except for, yknow, human readability permalink fedilink source parent [–] bandwidthcrisis@lemmy.world 3 points 3 days ago I've recently noticed web forms and appointment emails start to use that format. Maybe web devs are sneaking it in bit by bit. permalink fedilink source parent load more comments (1 reply) [–] merc@sh.itjust.works 63 points 3 days ago (2 children) As for why it's better: It's in sort order. Even if you use it for things that don't understand dates, they sort properly because the day is the last part, month is the middle part, and year is the first part. If you include hours, minutes or seconds, the sort order is still preserved. Speaking of things that don't understand dates, because there are no slashes, you can easily use it in file names, directories, and anything else that treats slash as a special character. In addition, if you include the time part, because it uses "T" to separate the date and time, it doesn't use a space, so once again it can be easily used anywhere where a space might cause issues. permalink fedilink source parent hideshow 4 child comments replies: [–] Rothe@piefed.social 10 points 3 days ago (2 children) ISO is better for archiving and sorting, inarguably so. But dd-mm-yyyy is better for day to day daily life usage, where the day and month are much more important than the year. Both have their uses, but for different situations. mm-dd-yyyy is just batshit though. permalink fedilink source parent hideshow 3 child comments replies: [–] merc@sh.itjust.works 3 points 3 days ago (1 child) But dd-mm-yyyy is better for day to day daily life usage Uh, no. permalink fedilink source parent hideshow 2 child comments replies: [–] Untamed_Star@lemmy.blahaj.zone 1 point 2 days ago (1 child) It literally just depends to what you are used to. permalink fedilink source parent hideshow 2 child comments replies: [–] merc@sh.itjust.works 3 points 2 days ago* (last edited 2 days ago) (1 child) Yes, ISO-8601 is objectively better than YYYY/DD/MM or MM/DD/YYYY or other strange formats. But, because it isn't the most widely used format, it can be less efficient when there's no danger of MM/DD vs DD/MM confusion. If person A is talking to person B and they're from the same culture, some culture-specific version like DD/MM/YY might be easier for them because it's what they're both used to, even if it is objectively inferior. But, if person A is talking to person C who is from a different place/culture things get more challenging because if the day of the month is 12 or under, it's hard to distinguish between DD/MM or MM/DD. Even if person C knows that person A comes from a place that does DD/MM, they don't know if person C used the native DD/MM format they're used to, or translated it to them to MM/DD because person A was trying to make things easy for person C. One of the advantages of the hyphens in ISO-8601, aside from them working with files, is that hyphens in dates are less common than slashes, so if someone sees 1212-11-12 they're more likely to understand that it's an ISO-formatted date. If they see 1212/11/12 it might be a MM/DD date or a DD/MM date. permalink fedilink source parent hideshow 2 child comments replies: [–] bookmeat@fedinsfw.app 1 point 2 days ago Start using it and suddenly it becomes most used. It is the little acts that make a difference. permalink fedilink source parent load more comments (1 reply) [–] raspberriesareyummy@lemmy.world 5 points 3 days ago (1 child) To be fair, the time separators don't behave well on all implementations of filesystem access by filename. Need to use underscores or omit them at times. permalink fedilink source parent hideshow 2 child comments replies: [–] libewa@feddit.org 3 points 3 days ago* (last edited 3 days ago) (1 child) And unlike most „forbidden characters“ for file names, the colon is actually used in NTFS: to separate the file path from the name of a named fork Alternate Data Stream. permalink fedilink source parent hideshow 2 child comments replies: [–] raspberriesareyummy@lemmy.world 3 points 3 days ago See, I hadn't even read about this. TIL :) Still, I use ISO8601 all the time when it comes to written dates :) permalink fedilink source parent [–] TootSweet@lemmy.world 28 points 4 days ago (1 child) This is the way. permalink fedilink source parent hideshow 2 child comments replies: [–] davidagain@lemmy.world 5 points 3 days ago (1 child) This is the way. permalink fedilink source parent hideshow 2 child comments replies: [–] bandwidthcrisis@lemmy.world 3 points 3 days ago This is the (year-month-) day. permalink fedilink source parent [–] trem@lemmy.blahaj.zone 15 points 4 days ago RFC 3339 permalink fedilink source parent [–] mkwt@lemmy.world 13 points 4 days ago (2 children) ISO would be great, but sadly OmegaStar doesn't support ISO timestamps yet. permalink fedilink source parent hideshow 4 child comments replies: [–] TrickDacy@lemmy.world 13 points 4 days ago (4 children) Wtf is an omega star? permalink fedilink source parent hideshow 5 child comments replies: [–] Viking_Hippie@lemmy.dbzer0.com 6 points 3 days ago The last star of the Greek alphabet? 🤷🏻 permalink fedilink source parent load more comments (3 replies) [–] bss03@infosec.pub 2 points 3 days ago "While Galactus has omniscient knowledge of all current user data providers, it doesn't have future sight" Just use EKS to deliver the feature this quarter, and block the OmegaStar migration on "the team gets their shit together" and supports ISO timestamps. permalink fedilink source parent [–] trainsrkool@lemmy.ml 6 points 3 days ago 💯 permalink fedilink source parent [–] wizardbeard@lemmy.dbzer0.com 4 points 4 days ago (8 children) Except I can't get behind the time part of it, personally. I can see the point of doing GMT with the offset if you're working across multiple timezones, but it's overkill for situations where you aren't. permalink fedilink source parent hideshow 10 child comments replies: [–] Dookieman12@piefed.social 12 points 4 days ago There's no way to predict how a date will be used. No reason not to be flexible. No reason to break convention. permalink fedilink source parent [–] Eq0@literature.cafe 7 points 4 days ago* (2 children) That’s how my brother missed a train: the linux planner used GMT while the local train company planner used assumed local time… So I disagree permalink fedilink source parent hideshow 3 child comments replies: [–] Cosmonaut_Collin@lemmy.world 3 points 3 days ago I think we should all, as a globe, just pick one time zone and use that. I don't care if my 1:00 pm is the middle of that night. Everyone's 5:00pm will be 5:00pm. We will learn how to adjust our schedules for the master time zone. permalink fedilink source parent load more comments (1 reply) load more comments (6 replies) load more comments (28 replies)
[–] 7EP6vuI@feddit.org 200 points 4 days ago (7 children) ISO 8601 YYYY-MM-DD permalink fedilink source parent hideshow 13 child comments replies: [–] jlow@slrpnk.net 46 points 4 days ago 👆 permalink fedilink source parent [–] GreyEyedGhost@piefed.ca 16 points 3 days ago (2 children) RFC 3339 FTW! Open source, and no ambiguous options grandfathered in. permalink fedilink source parent hideshow 4 child comments replies: [–] bss03@infosec.pub 5 points 3 days ago Was looking for this. Yes. Whenever possible, dates should be specified in a format that is BOTH RFC 3339 and ISO 8601. I'd say both have their quirks, but the intersection of the grammars is machine-parseable and human-readable without (much) legacy baggage or (much) experimental / reserved-for-future-use noise. permalink fedilink source parent [–] The_Decryptor@aussie.zone 2 points 3 days ago Though the way it specifies raw UTC times is odd (8601 uses Z, 3339 uses -00:00), that got changed with RFC 9557 to align with 8601. It also supports "zoned date times", where instead of just using the UTC offset, you can also include a timezone identifier, e.g. 2020-01-01T00:00+01:00[Europe/Paris]. Useful if you're doing calculations on dates but can be ignored otherwise. permalink fedilink source parent [–] plasma8726@lemmy.today 13 points 3 days ago This is the only way to date. permalink fedilink source parent [–] CanadianCarl@sh.itjust.works 1 point 2 days ago ISO week date permalink fedilink source parent [–] Iusedtobeanalien@lemmy.world 3 points 3 days ago (1 child) No need for dashes permalink fedilink source parent hideshow 2 child comments replies: [–] sem@piefed.blahaj.zone 4 points 3 days ago Except for, yknow, human readability permalink fedilink source parent [–] bandwidthcrisis@lemmy.world 3 points 3 days ago I've recently noticed web forms and appointment emails start to use that format. Maybe web devs are sneaking it in bit by bit. permalink fedilink source parent load more comments (1 reply)
[–] GreyEyedGhost@piefed.ca 16 points 3 days ago (2 children) RFC 3339 FTW! Open source, and no ambiguous options grandfathered in. permalink fedilink source parent hideshow 4 child comments replies: [–] bss03@infosec.pub 5 points 3 days ago Was looking for this. Yes. Whenever possible, dates should be specified in a format that is BOTH RFC 3339 and ISO 8601. I'd say both have their quirks, but the intersection of the grammars is machine-parseable and human-readable without (much) legacy baggage or (much) experimental / reserved-for-future-use noise. permalink fedilink source parent [–] The_Decryptor@aussie.zone 2 points 3 days ago Though the way it specifies raw UTC times is odd (8601 uses Z, 3339 uses -00:00), that got changed with RFC 9557 to align with 8601. It also supports "zoned date times", where instead of just using the UTC offset, you can also include a timezone identifier, e.g. 2020-01-01T00:00+01:00[Europe/Paris]. Useful if you're doing calculations on dates but can be ignored otherwise. permalink fedilink source parent
[–] bss03@infosec.pub 5 points 3 days ago Was looking for this. Yes. Whenever possible, dates should be specified in a format that is BOTH RFC 3339 and ISO 8601. I'd say both have their quirks, but the intersection of the grammars is machine-parseable and human-readable without (much) legacy baggage or (much) experimental / reserved-for-future-use noise. permalink fedilink source parent
[–] The_Decryptor@aussie.zone 2 points 3 days ago Though the way it specifies raw UTC times is odd (8601 uses Z, 3339 uses -00:00), that got changed with RFC 9557 to align with 8601. It also supports "zoned date times", where instead of just using the UTC offset, you can also include a timezone identifier, e.g. 2020-01-01T00:00+01:00[Europe/Paris]. Useful if you're doing calculations on dates but can be ignored otherwise. permalink fedilink source parent
[–] plasma8726@lemmy.today 13 points 3 days ago This is the only way to date. permalink fedilink source parent
[–] Iusedtobeanalien@lemmy.world 3 points 3 days ago (1 child) No need for dashes permalink fedilink source parent hideshow 2 child comments replies: [–] sem@piefed.blahaj.zone 4 points 3 days ago Except for, yknow, human readability permalink fedilink source parent
[–] sem@piefed.blahaj.zone 4 points 3 days ago Except for, yknow, human readability permalink fedilink source parent
[–] bandwidthcrisis@lemmy.world 3 points 3 days ago I've recently noticed web forms and appointment emails start to use that format. Maybe web devs are sneaking it in bit by bit. permalink fedilink source parent
[–] merc@sh.itjust.works 63 points 3 days ago (2 children) As for why it's better: It's in sort order. Even if you use it for things that don't understand dates, they sort properly because the day is the last part, month is the middle part, and year is the first part. If you include hours, minutes or seconds, the sort order is still preserved. Speaking of things that don't understand dates, because there are no slashes, you can easily use it in file names, directories, and anything else that treats slash as a special character. In addition, if you include the time part, because it uses "T" to separate the date and time, it doesn't use a space, so once again it can be easily used anywhere where a space might cause issues. permalink fedilink source parent hideshow 4 child comments replies: [–] Rothe@piefed.social 10 points 3 days ago (2 children) ISO is better for archiving and sorting, inarguably so. But dd-mm-yyyy is better for day to day daily life usage, where the day and month are much more important than the year. Both have their uses, but for different situations. mm-dd-yyyy is just batshit though. permalink fedilink source parent hideshow 3 child comments replies: [–] merc@sh.itjust.works 3 points 3 days ago (1 child) But dd-mm-yyyy is better for day to day daily life usage Uh, no. permalink fedilink source parent hideshow 2 child comments replies: [–] Untamed_Star@lemmy.blahaj.zone 1 point 2 days ago (1 child) It literally just depends to what you are used to. permalink fedilink source parent hideshow 2 child comments replies: [–] merc@sh.itjust.works 3 points 2 days ago* (last edited 2 days ago) (1 child) Yes, ISO-8601 is objectively better than YYYY/DD/MM or MM/DD/YYYY or other strange formats. But, because it isn't the most widely used format, it can be less efficient when there's no danger of MM/DD vs DD/MM confusion. If person A is talking to person B and they're from the same culture, some culture-specific version like DD/MM/YY might be easier for them because it's what they're both used to, even if it is objectively inferior. But, if person A is talking to person C who is from a different place/culture things get more challenging because if the day of the month is 12 or under, it's hard to distinguish between DD/MM or MM/DD. Even if person C knows that person A comes from a place that does DD/MM, they don't know if person C used the native DD/MM format they're used to, or translated it to them to MM/DD because person A was trying to make things easy for person C. One of the advantages of the hyphens in ISO-8601, aside from them working with files, is that hyphens in dates are less common than slashes, so if someone sees 1212-11-12 they're more likely to understand that it's an ISO-formatted date. If they see 1212/11/12 it might be a MM/DD date or a DD/MM date. permalink fedilink source parent hideshow 2 child comments replies: [–] bookmeat@fedinsfw.app 1 point 2 days ago Start using it and suddenly it becomes most used. It is the little acts that make a difference. permalink fedilink source parent load more comments (1 reply) [–] raspberriesareyummy@lemmy.world 5 points 3 days ago (1 child) To be fair, the time separators don't behave well on all implementations of filesystem access by filename. Need to use underscores or omit them at times. permalink fedilink source parent hideshow 2 child comments replies: [–] libewa@feddit.org 3 points 3 days ago* (last edited 3 days ago) (1 child) And unlike most „forbidden characters“ for file names, the colon is actually used in NTFS: to separate the file path from the name of a named fork Alternate Data Stream. permalink fedilink source parent hideshow 2 child comments replies: [–] raspberriesareyummy@lemmy.world 3 points 3 days ago See, I hadn't even read about this. TIL :) Still, I use ISO8601 all the time when it comes to written dates :) permalink fedilink source parent
[–] Rothe@piefed.social 10 points 3 days ago (2 children) ISO is better for archiving and sorting, inarguably so. But dd-mm-yyyy is better for day to day daily life usage, where the day and month are much more important than the year. Both have their uses, but for different situations. mm-dd-yyyy is just batshit though. permalink fedilink source parent hideshow 3 child comments replies: [–] merc@sh.itjust.works 3 points 3 days ago (1 child) But dd-mm-yyyy is better for day to day daily life usage Uh, no. permalink fedilink source parent hideshow 2 child comments replies: [–] Untamed_Star@lemmy.blahaj.zone 1 point 2 days ago (1 child) It literally just depends to what you are used to. permalink fedilink source parent hideshow 2 child comments replies: [–] merc@sh.itjust.works 3 points 2 days ago* (last edited 2 days ago) (1 child) Yes, ISO-8601 is objectively better than YYYY/DD/MM or MM/DD/YYYY or other strange formats. But, because it isn't the most widely used format, it can be less efficient when there's no danger of MM/DD vs DD/MM confusion. If person A is talking to person B and they're from the same culture, some culture-specific version like DD/MM/YY might be easier for them because it's what they're both used to, even if it is objectively inferior. But, if person A is talking to person C who is from a different place/culture things get more challenging because if the day of the month is 12 or under, it's hard to distinguish between DD/MM or MM/DD. Even if person C knows that person A comes from a place that does DD/MM, they don't know if person C used the native DD/MM format they're used to, or translated it to them to MM/DD because person A was trying to make things easy for person C. One of the advantages of the hyphens in ISO-8601, aside from them working with files, is that hyphens in dates are less common than slashes, so if someone sees 1212-11-12 they're more likely to understand that it's an ISO-formatted date. If they see 1212/11/12 it might be a MM/DD date or a DD/MM date. permalink fedilink source parent hideshow 2 child comments replies: [–] bookmeat@fedinsfw.app 1 point 2 days ago Start using it and suddenly it becomes most used. It is the little acts that make a difference. permalink fedilink source parent load more comments (1 reply)
[–] merc@sh.itjust.works 3 points 3 days ago (1 child) But dd-mm-yyyy is better for day to day daily life usage Uh, no. permalink fedilink source parent hideshow 2 child comments replies: [–] Untamed_Star@lemmy.blahaj.zone 1 point 2 days ago (1 child) It literally just depends to what you are used to. permalink fedilink source parent hideshow 2 child comments replies: [–] merc@sh.itjust.works 3 points 2 days ago* (last edited 2 days ago) (1 child) Yes, ISO-8601 is objectively better than YYYY/DD/MM or MM/DD/YYYY or other strange formats. But, because it isn't the most widely used format, it can be less efficient when there's no danger of MM/DD vs DD/MM confusion. If person A is talking to person B and they're from the same culture, some culture-specific version like DD/MM/YY might be easier for them because it's what they're both used to, even if it is objectively inferior. But, if person A is talking to person C who is from a different place/culture things get more challenging because if the day of the month is 12 or under, it's hard to distinguish between DD/MM or MM/DD. Even if person C knows that person A comes from a place that does DD/MM, they don't know if person C used the native DD/MM format they're used to, or translated it to them to MM/DD because person A was trying to make things easy for person C. One of the advantages of the hyphens in ISO-8601, aside from them working with files, is that hyphens in dates are less common than slashes, so if someone sees 1212-11-12 they're more likely to understand that it's an ISO-formatted date. If they see 1212/11/12 it might be a MM/DD date or a DD/MM date. permalink fedilink source parent hideshow 2 child comments replies: [–] bookmeat@fedinsfw.app 1 point 2 days ago Start using it and suddenly it becomes most used. It is the little acts that make a difference. permalink fedilink source parent
[–] Untamed_Star@lemmy.blahaj.zone 1 point 2 days ago (1 child) It literally just depends to what you are used to. permalink fedilink source parent hideshow 2 child comments replies: [–] merc@sh.itjust.works 3 points 2 days ago* (last edited 2 days ago) (1 child) Yes, ISO-8601 is objectively better than YYYY/DD/MM or MM/DD/YYYY or other strange formats. But, because it isn't the most widely used format, it can be less efficient when there's no danger of MM/DD vs DD/MM confusion. If person A is talking to person B and they're from the same culture, some culture-specific version like DD/MM/YY might be easier for them because it's what they're both used to, even if it is objectively inferior. But, if person A is talking to person C who is from a different place/culture things get more challenging because if the day of the month is 12 or under, it's hard to distinguish between DD/MM or MM/DD. Even if person C knows that person A comes from a place that does DD/MM, they don't know if person C used the native DD/MM format they're used to, or translated it to them to MM/DD because person A was trying to make things easy for person C. One of the advantages of the hyphens in ISO-8601, aside from them working with files, is that hyphens in dates are less common than slashes, so if someone sees 1212-11-12 they're more likely to understand that it's an ISO-formatted date. If they see 1212/11/12 it might be a MM/DD date or a DD/MM date. permalink fedilink source parent hideshow 2 child comments replies: [–] bookmeat@fedinsfw.app 1 point 2 days ago Start using it and suddenly it becomes most used. It is the little acts that make a difference. permalink fedilink source parent
[–] merc@sh.itjust.works 3 points 2 days ago* (last edited 2 days ago) (1 child) Yes, ISO-8601 is objectively better than YYYY/DD/MM or MM/DD/YYYY or other strange formats. But, because it isn't the most widely used format, it can be less efficient when there's no danger of MM/DD vs DD/MM confusion. If person A is talking to person B and they're from the same culture, some culture-specific version like DD/MM/YY might be easier for them because it's what they're both used to, even if it is objectively inferior. But, if person A is talking to person C who is from a different place/culture things get more challenging because if the day of the month is 12 or under, it's hard to distinguish between DD/MM or MM/DD. Even if person C knows that person A comes from a place that does DD/MM, they don't know if person C used the native DD/MM format they're used to, or translated it to them to MM/DD because person A was trying to make things easy for person C. One of the advantages of the hyphens in ISO-8601, aside from them working with files, is that hyphens in dates are less common than slashes, so if someone sees 1212-11-12 they're more likely to understand that it's an ISO-formatted date. If they see 1212/11/12 it might be a MM/DD date or a DD/MM date. permalink fedilink source parent hideshow 2 child comments replies: [–] bookmeat@fedinsfw.app 1 point 2 days ago Start using it and suddenly it becomes most used. It is the little acts that make a difference. permalink fedilink source parent
[–] bookmeat@fedinsfw.app 1 point 2 days ago Start using it and suddenly it becomes most used. It is the little acts that make a difference. permalink fedilink source parent
[–] raspberriesareyummy@lemmy.world 5 points 3 days ago (1 child) To be fair, the time separators don't behave well on all implementations of filesystem access by filename. Need to use underscores or omit them at times. permalink fedilink source parent hideshow 2 child comments replies: [–] libewa@feddit.org 3 points 3 days ago* (last edited 3 days ago) (1 child) And unlike most „forbidden characters“ for file names, the colon is actually used in NTFS: to separate the file path from the name of a named fork Alternate Data Stream. permalink fedilink source parent hideshow 2 child comments replies: [–] raspberriesareyummy@lemmy.world 3 points 3 days ago See, I hadn't even read about this. TIL :) Still, I use ISO8601 all the time when it comes to written dates :) permalink fedilink source parent
[–] libewa@feddit.org 3 points 3 days ago* (last edited 3 days ago) (1 child) And unlike most „forbidden characters“ for file names, the colon is actually used in NTFS: to separate the file path from the name of a named fork Alternate Data Stream. permalink fedilink source parent hideshow 2 child comments replies: [–] raspberriesareyummy@lemmy.world 3 points 3 days ago See, I hadn't even read about this. TIL :) Still, I use ISO8601 all the time when it comes to written dates :) permalink fedilink source parent
[–] raspberriesareyummy@lemmy.world 3 points 3 days ago See, I hadn't even read about this. TIL :) Still, I use ISO8601 all the time when it comes to written dates :) permalink fedilink source parent
[–] TootSweet@lemmy.world 28 points 4 days ago (1 child) This is the way. permalink fedilink source parent hideshow 2 child comments replies: [–] davidagain@lemmy.world 5 points 3 days ago (1 child) This is the way. permalink fedilink source parent hideshow 2 child comments replies: [–] bandwidthcrisis@lemmy.world 3 points 3 days ago This is the (year-month-) day. permalink fedilink source parent
[–] davidagain@lemmy.world 5 points 3 days ago (1 child) This is the way. permalink fedilink source parent hideshow 2 child comments replies: [–] bandwidthcrisis@lemmy.world 3 points 3 days ago This is the (year-month-) day. permalink fedilink source parent
[–] bandwidthcrisis@lemmy.world 3 points 3 days ago This is the (year-month-) day. permalink fedilink source parent
[–] mkwt@lemmy.world 13 points 4 days ago (2 children) ISO would be great, but sadly OmegaStar doesn't support ISO timestamps yet. permalink fedilink source parent hideshow 4 child comments replies: [–] TrickDacy@lemmy.world 13 points 4 days ago (4 children) Wtf is an omega star? permalink fedilink source parent hideshow 5 child comments replies: [–] Viking_Hippie@lemmy.dbzer0.com 6 points 3 days ago The last star of the Greek alphabet? 🤷🏻 permalink fedilink source parent load more comments (3 replies) [–] bss03@infosec.pub 2 points 3 days ago "While Galactus has omniscient knowledge of all current user data providers, it doesn't have future sight" Just use EKS to deliver the feature this quarter, and block the OmegaStar migration on "the team gets their shit together" and supports ISO timestamps. permalink fedilink source parent
[–] TrickDacy@lemmy.world 13 points 4 days ago (4 children) Wtf is an omega star? permalink fedilink source parent hideshow 5 child comments replies: [–] Viking_Hippie@lemmy.dbzer0.com 6 points 3 days ago The last star of the Greek alphabet? 🤷🏻 permalink fedilink source parent load more comments (3 replies)
[–] Viking_Hippie@lemmy.dbzer0.com 6 points 3 days ago The last star of the Greek alphabet? 🤷🏻 permalink fedilink source parent
[–] bss03@infosec.pub 2 points 3 days ago "While Galactus has omniscient knowledge of all current user data providers, it doesn't have future sight" Just use EKS to deliver the feature this quarter, and block the OmegaStar migration on "the team gets their shit together" and supports ISO timestamps. permalink fedilink source parent
[–] wizardbeard@lemmy.dbzer0.com 4 points 4 days ago (8 children) Except I can't get behind the time part of it, personally. I can see the point of doing GMT with the offset if you're working across multiple timezones, but it's overkill for situations where you aren't. permalink fedilink source parent hideshow 10 child comments replies: [–] Dookieman12@piefed.social 12 points 4 days ago There's no way to predict how a date will be used. No reason not to be flexible. No reason to break convention. permalink fedilink source parent [–] Eq0@literature.cafe 7 points 4 days ago* (2 children) That’s how my brother missed a train: the linux planner used GMT while the local train company planner used assumed local time… So I disagree permalink fedilink source parent hideshow 3 child comments replies: [–] Cosmonaut_Collin@lemmy.world 3 points 3 days ago I think we should all, as a globe, just pick one time zone and use that. I don't care if my 1:00 pm is the middle of that night. Everyone's 5:00pm will be 5:00pm. We will learn how to adjust our schedules for the master time zone. permalink fedilink source parent load more comments (1 reply) load more comments (6 replies)
[–] Dookieman12@piefed.social 12 points 4 days ago There's no way to predict how a date will be used. No reason not to be flexible. No reason to break convention. permalink fedilink source parent
[–] Eq0@literature.cafe 7 points 4 days ago* (2 children) That’s how my brother missed a train: the linux planner used GMT while the local train company planner used assumed local time… So I disagree permalink fedilink source parent hideshow 3 child comments replies: [–] Cosmonaut_Collin@lemmy.world 3 points 3 days ago I think we should all, as a globe, just pick one time zone and use that. I don't care if my 1:00 pm is the middle of that night. Everyone's 5:00pm will be 5:00pm. We will learn how to adjust our schedules for the master time zone. permalink fedilink source parent load more comments (1 reply)
[–] Cosmonaut_Collin@lemmy.world 3 points 3 days ago I think we should all, as a globe, just pick one time zone and use that. I don't care if my 1:00 pm is the middle of that night. Everyone's 5:00pm will be 5:00pm. We will learn how to adjust our schedules for the master time zone. permalink fedilink source parent
