• 0 Posts
  • 15 Comments
Joined 3 months ago
cake
Cake day: October 26th, 2024

help-circle




  • azolus@slrpnk.netto196@lemmy.blahaj.zoneISO 8601 ftw rule
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    10 days ago

    2025-01-26 so it’s 26.01. It’s easy to look up. All you need to know is that the date goes YYY-MM-DD (year -> month -> day). You do the same thing when you write 26.01 instead of 26.01.2025, since you are just dropping information about the year.

    Starting out with “you can’t change my mind” is fine but then don’t argue for your point with arguments that can easily be debunked. Use whichever format you like better but don’t pretend that’s more than personal preference at that point.

    The big argument for the iso date-time format is lexicographic ordering. If you don’t care about that, then don’t use it.

    Just as a side-note: some european countries were in fact considering switching to the iso date-time format but didn’t because it would have been an inconvenience to people already familiar with different formats. Basically the “it’s better but people prefer the older format” thing we have going on in the comment sections right now.

    Cheers











  • I’d say going with C is not a bad idea at all—I for one would be interested. C is not going to become obsolete any time soon and is an immensly useful language to be proficient in.

    When I tried to learn C I felt like I’m doing everything wrong because the C-way of doing things is very different to what one is used to from more modern languages (header files, make etc). Bridging the gap between the “I can solve project euler challenges” stage and actually being able to organize and implement proper projects is difficult without a mentor, so why not share your expertise?

    In the end, go with what you feel most like doing, there will be an audience either way. So pick what is most fun to you!