Yeah, I seem to remember that architecture code is done little endian, and the network stack is big endian. Then there is bi-endian, which I have no clue how that works.
- 0 Posts
- 4 Comments
Joined 3 years ago
Cake day: June 18th, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
I’d much rather have consistency. If yyyymmdd is the best solution for file names, it’s the best across the board.
I’ve been using yyyymmdd and was appalled when I found out the ones appaled by the American method uses ddmmyyyy. It doesn’t even sort chronologicaly in alpha numeric ordering. Just why???
Edit: I just realized that ddmmyyyy looks like dummy and that’s how I’m going to refer to it from now on.



Here in the states we use short hand usually. So your date would just be stated as, “March 12th”. Long format would start off as, “in the year 2026 AD/CE…” which is usually done in things like proclamations by local governments for naming a specific day in someone’s honor.
For previous and current dates, people definitely use mmddyyyy and I don’t like it. I would much prefer to use something along the line of star-dates from star trek time expressed in years only: 2026.19178 (March 12 00:00). This fixes the need for leap years/days/seconds in calendars and instead dates become accurate.