The Google sheets and excel sort works because the coders have specifically programmed to detect every popular date format and internally convert it to the objectively best format
True, but it's obviously best to have 1 standard for date formatting and that's really the most important factor I can think of
99.99+% of all software are used by non coders. And as coders, it is our job to make our software as easy and pleasant to use as possible for all of our users :)
As long as DDMMYYYY is the standard, we will adhere to that standard and put in the extra work on our side so the users won't have to
Just because someone else spent a lot of effort solving a problem that didn't need to exist in the first place doesn't make it a trivial problem to have solved and still be having to solve. The labor hours wasted on supporting batshit time formats is absurd. Even BEFORE you include all the hours wasted on bugs and side effects and issues (which in some cases have literally killed people) that resulted from just not using a sane format.
I'm fine with 2 systems, DD/MM/YYYY for general use because that's a good format for personal scheduling, but YYYY/MM/DD hh:mm:ss for anything involving work or industry because having the year first is useful for maintaining historical data.
Starting with the biggest bucket and searching down from there can save a lot of compute and search time.
Because we don't sort any list or value by incrementing the leftmost digit most. On top of that dd mm yy actually increments the second most, then the first, then the 4th, then the 3rd, then the 8th 7th 6th 5th.
Do you want to write the time as seconds minutes hours or minutes seconds hours or just keep it logically hhmmss?
I mean at the end of the day everything is just a means of conveying information so as long as it does ok at doing that you do you boo it's all preference and I'm fine however. But when it's a STANDARD. Nah fam. We do that shit the proper way.
Spend about 5 minutes developing software to handle dates and times (not using libraries written by people who have screamed into the void about shooting anyone not using ISO 8601 and/or digital time standards like the unix timestamp beginning at/referencing seconds since 1970-01-01T00:00:00Z. (In super simplified terms)
Seriously anyone who has written those libraries to handle peoples fucked up varieties of timestamps might possibly murder anyone around when it's mentioned if someone implies any other time standard "isn't a big deal". It's grade A high quality trauma working on those.
deleted by creator
So that, when you enter the dates into a database and sort them, they go into chronological order.
deleted by creator
When you write code and call any language's default
sortfunction, it will correctly sort YYYYMMDD but not DDMMYYYYThe Google sheets and excel sort works because the coders have specifically programmed to detect every popular date format and then sort accordingly
The Google sheets and excel sort works because the coders have specifically programmed to detect every popular date format and internally convert it to the objectively best format
deleted by creator
True, but it's obviously best to have 1 standard for date formatting and that's really the most important factor I can think of
99.99+% of all software are used by non coders. And as coders, it is our job to make our software as easy and pleasant to use as possible for all of our users :)
As long as DDMMYYYY is the standard, we will adhere to that standard and put in the extra work on our side so the users won't have to
Just because someone else spent a lot of effort solving a problem that didn't need to exist in the first place doesn't make it a trivial problem to have solved and still be having to solve. The labor hours wasted on supporting batshit time formats is absurd. Even BEFORE you include all the hours wasted on bugs and side effects and issues (which in some cases have literally killed people) that resulted from just not using a sane format.
Nah, it falls apart if you include time. YYYYMMDD hh:mm:ss makes more sense than DD/MM/YYYY hh:mm:ss.
how often do you write dates including the time? unless you're a programmer ddmmyyyy is obviously the easiest to use
Death to America
I'm fine with 2 systems, DD/MM/YYYY for general use because that's a good format for personal scheduling, but YYYY/MM/DD hh:mm:ss for anything involving work or industry because having the year first is useful for maintaining historical data.
Starting with the biggest bucket and searching down from there can save a lot of compute and search time.
Because we don't sort any list or value by incrementing the leftmost digit most. On top of that dd mm yy actually increments the second most, then the first, then the 4th, then the 3rd, then the 8th 7th 6th 5th. Do you want to write the time as seconds minutes hours or minutes seconds hours or just keep it logically hhmmss?
I mean at the end of the day everything is just a means of conveying information so as long as it does ok at doing that you do you boo it's all preference and I'm fine however. But when it's a STANDARD. Nah fam. We do that shit the proper way. Spend about 5 minutes developing software to handle dates and times (not using libraries written by people who have screamed into the void about shooting anyone not using ISO 8601 and/or digital time standards like the unix timestamp beginning at/referencing seconds since 1970-01-01T00:00:00Z. (In super simplified terms)
Seriously anyone who has written those libraries to handle peoples fucked up varieties of timestamps might possibly murder anyone around when it's mentioned if someone implies any other time standard "isn't a big deal". It's grade A high quality trauma working on those.