Okay if you scroll enough, it goes from year 2 to 1 to 2 and starts getting higher. I went to 1582 again and this seems to be correct
Comment on The lost days
BudgetBandit@sh.itjust.works 3 months ago
Huh… weird
BudgetBandit@sh.itjust.works 3 months ago
BudgetBandit@sh.itjust.works 3 months ago
And no, it does not roll around, it seems to really be BC because my appointments are not listed
Sibbo@sopuli.xyz 3 months ago
You should get an award for doing meticulous and careful research.
AbsolutelyNotAVelociraptor@sh.itjust.works 3 months ago
here, have my gold for your effort.Lemmy gold
wolfpack86@lemmy.world 3 months ago
And you have a leap year in a non even year
cannedtuna@lemmy.world 3 months ago
brbposting@sh.itjust.works 3 months ago
This is the final straw with Apple software bugs
EVERYONE* impacted by this, you know your duty -> apple.com/feedback
* yes, even you Bartholomew
raccoon@sh.itjust.works 3 months ago
Gork@lemm.ee 3 months ago
This bothers me way more than it really should.
We should pressure them to make a fix for it.
Mesophar@lemm.ee 3 months ago
What’s the fix…? o.o
Passerby6497@lemmy.world 3 months ago
CHANGING TIME ITSELF
sp3tr4l@lemmy.zip 3 months ago
Yep!
britannica.com/…/ten-days-that-vanished-the-switc…
This is not some kind of software bug, it actually reflects how the real, western calendar system was intentionally designed.
Don’t let modern doomsday cults/prophets know about it though, wouldn’t want to further confuse their Bible Math.
Other quirks of our calendar system:
There is no year 0.
en.m.wikipedia.org/wiki/Year_zero
Goes straight from 1 BC to 1 AD.
This is why the new millenium actually began in 2001, not 2000.
WolfLink@sh.itjust.works 3 months ago
Yo some poor programmer had to manually code this in there
amon@lemmy.world 3 months ago
whilst being screamed at by SJ to get it done
dan@upvote.au 3 months ago
Most developers don’t write their own date handling code; they instead use code that someone else already wrote.
BeardedGingerWonder@feddit.uk 2 months ago
Right, but the original person who wrote the code everyone uses still had to program it in.
themoonisacheese@sh.itjust.works 3 months ago
Also, Jesus probably wasn’t born in 1AD. as a matter of fact is 1AD the year after Christmas where Jesus was born (so he was born in 1BC) or was Jesus not born for the vast majority of 1AD until a week before the end of year?
Crazy what assimilating pagan holidays will do to a religion
eRac@lemmings.world 3 months ago
Jesus was born in the spring, not the winter. Christmas is an adaptation of northern winter festivities and they slapped a Christian justification on it.
froh42@lemmy.world 3 months ago
I always thought it was the christian brand version of Roman Saturnalia.
Sineljora@sh.itjust.works 3 months ago
Jesus was never real and was not recorded by dozens of scribes that were in the place at the same time (one famous example was debunked hundreds of years ago). He’s a sun-god astrological myth, like Horus and others before and they all share similar attributes.
His purpose was to signal the start of the age of Pisces (two fish), and the winter solstice will see the sun rise (after 3 days of apparent stagnation) in the Aquarius constellation in 2150 or so. His resurrection is celebrated at Spring equinox, or Easter, when the sun finally overpowers the darkness.
MBM@lemmings.world 3 months ago
And that’s if they had managed to get Jesus’s birth year right, but he was actually born a couple of years BC
TempermentalAnomaly@lemmy.world 3 months ago
Can’t believe we skipped both 0 BC and 0 AD.
In all seriousness, we can define the millennium to start on 2000 and work from there. We already do this with decades and centuries.
InFerNo@lemmy.ml 3 months ago
Just happened to help my 9yo with his homework and they’re learning that centuries are defined as starting at year 1 and ending with a 0.
101 200
1401 1500
Etc
TempermentalAnomaly@lemmy.world 3 months ago
But it’s arbitrary. It doesn’t need to. Centuries are just 100 years. Start at years ending in one or zero.