That’s a lot of tradition to discard.
The height of tides are rooted in this but have 7 day periods of increasing, decreasing, increasing, decreasing.
I don't know if thats reason enough to continue with it, but possibly part of the history
But the more reasonable proposal I heard was just to call it New Years Day/Weekend, depending?
Referring to “boaty mcboatface”
For example, “our next meeting is w48.3” is much more understandable than “day 339”.
Perhaps weeks seems to make sense since we sometimes use them for offsets and ranges, like "this project will take 6 weeks" and figuring out how many days that is is inconvenient. But if we were using days then we simply wouldn't use groups of 30 or 7 for things like that, we would use groups and multiples of 10 or 5. We'd probably end up using kilodays and millidays too instead of years or minutes, and years would be arbitrary, but 51.9something weeks is already arbitrary anyways.
And as that # of weeks example just showed, .day is ambiguous with decimal fractions of a unit.
All in all I see no special obvious rightness here. It's kinda crap actually.
or 365.2425 one day months and no squabbles every 400 years. (we will however be squabbling the entire rest of the time)
Aside from Halloween and NYE it will be very easy for people to get used to a 28 day month.
Calling today 44.7 means that we're effectively using base 7 after the decimal point (but it's 1 through 7 instead of the usual 0 through 6, for extra fun), while using base 10 before it.
Why not just something nice and easy-to-parse without all the mathematical confusion, like "44d7"?
how about 5Nov44d7, much easier to parse. go with 5Nov43d6 and I'm on board even quicker because I prefer 0 indexing.
That dot has many interpretations; in dates, sometimes it separates the month from year, or the day from a month. In version numbers, it separates major from minor, etc.
It's so much not a "decimal point", that in some languages (Hungarian and German, for instance) it is a thousands separator, whereas for decimal fractions a comma is used (10,000.00 in English is 10.000,00 in Hungarian, making Excel flip)
It is really just a dot. Our interpretation is what makes it a certain kind of separator. Or not a separator at all, like at the end of this sentence.
Numbers with a dot or comma means it's decimal. Your date reference makes no sence because either / or - is used in those cases, not dots or comma's.
Basically, having a dot or comma adds to the confusion when working with non decimal numbers.
In my (european) country a dot is used - for example 5.11.2023.
w36:2
But it wouldn't cause nearly as much confusion or decimal place issues relating to improper automation.
But... It doesn't in IP addresses, version numbers, dates, with different locales, and possibly many other uses.
These examples clearly show that "numbers with a dot" doesn't always mean decimal.
A dot is a dot. Mainly with the _role_ of a separator. When you interpret it, it might mean a _decimal_ separator for you, but as well might mean a thousand-separator for MS excel with the German locale.
You’re not playing cricket, I guess. There, an over is six throws, and 4.3 overs is four and an half over.
Having worked in banking and hedge funds for many years for US, UK and European firms i have never once encountered this ISO calendar. I also part trained as an auditor when i started out, similarly never saw this. In fact this is the first time I've ever heard of it.
They do sometimes pretend each month is 30 days though.
And keep the named 7-day week cycle as-is independently of that, this one has been going for millenia and we need some weekends after all
year/day/hectosecond.second(.millisecond and so on to the desired precision)
The current date-time, to the second, would be 2023/308/342.65
The days, like the years and second-based units, are 0-indexed.
There are 100 seconds in a hectosecond, and normally 864 hectoseconds in a day.
And to go with it, I'd advocate either a "3-on, 2-off", or "6-on, 4-off" work cycle, depending on the nature of the work, or even just personal preference. This way, today(308) would obviously be on a "weekend" either way.
Actually, looking it up now it looks like the usage of the name "Julian" is due to the way the old tracking systems were programmed and used "JDATE" or similar. Nowadays it's just burned in habit that it's called the Julian Date.
My guess is that the idea of counting days attached the "Julian" name to day number in a year.
The one where there are years without a new year’s day, and years with two?
https://en.wikipedia.org/wiki/ISO_8601#Week_dates
“As a consequence, if 1 January is on a Monday, Tuesday, Wednesday or Thursday, it is in week 01. If 1 January is on a Friday, Saturday or Sunday, it is in week 52 or 53 of the previous year (there is no week 00). 28 December is always in the last week of its year.”
The problem is mapping it to your legacy calendar holiday, which like everything else is going to vary somewhat year by year.
a new calendar not mapping cleanly to the current months hardly seems like a valid criticism of a calendar that intentionally doesn't map to the current months.
This way, people can play with legacy dates for their birthdays, religious observances, etc but use a sane system at all other times. This already happens with Chinese/Islamic calendars anyways, Chinese new year is a date I have to look up every year, and that’s OK because the calendar is used for literally nothing else outside traditional festivals. Optimise for the common case, after all. Christmas is w52.1 this year, w52.3 the next, etc, just as CNY is 22-jan and 10-feb this and next year (but 1/1 on the Chinese calendar).
The only trouble is that some years have 52 weeks and some 53, but such is the price to pay for backwards compatibility.