this post was submitted on 31 Dec 2025
443 points (92.4% liked)
Comic Strips
20802 readers
3095 users here now
Comic Strips is a community for those who love comic stories.
The rules are simple:
- The post can be a single image, an image gallery, or a link to a specific comic hosted on another site (the author's website, for instance).
- The comic must be a complete story.
- If it is an external link, it must be to a specific story, not to the root of the site.
- You may post comics from others or your own.
- If you are posting a comic of your own, a maximum of one per week is allowed (I know, your comics are great, but this rule helps avoid spam).
- The comic can be in any language, but if it's not in English, OP must include an English translation in the post's 'body' field (note: you don't need to select a specific language when posting a comic).
- Politeness.
- AI-generated comics aren't allowed.
- Adult content is not allowed. This community aims to be fun for people of all ages.
Web of links
- !linuxmemes@lemmy.world: "I use Arch btw"
- !memes@lemmy.world: memes (you don't say!)
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It'd still be a mess anyway. How do you subdivide your two year halves? What do your months look like? If they still exist.
Assuming you use equinoxes too, you can split your year in 4... Except since you've got 365 days to split, it will never be a perfect split.
And turns out the Earth doesn't care about synchronizing rotation and revolution and the year is actually about 365.24 days. so you still have freaking leap days every four years, except not every hundred year, except yes please every 400. Or whatever rule you make to fix the inevitable deviation.
I mean we define year as being from one spring equinox¹ to the next, no matter if it's 365 or 366 days. So if we made next year 1 it would be from 20th of March 2026 14:46 UTC to the next 20th of march 2027 20:25 UTC (The first day of the year could be day 0, the last of the old year but still also in new year, to account for the fact that it's not midnight.). The months would be replaced with quarters(seasons), ending on: June 21, September 23, December 21. Every year the dates would slightly shift because of the way orbits work, but there is no leap year math.
The first quarter, spring, has 93 days, the second, summer, 94 and so on. These will probably be subdivided a multitude of ways. Quickly sketching I found 6 * 4 * 4 - (3 or 4) which seems to work, though I'm naturally draw to base6 due to it being highly composite. This makes 24 days in a quarter-season. A nice analogue to the hours.
I think this calendar works better because it doesn't attempt to add any human control over a completely chaotic system: Earths orbit speed and rotational period. The underlying principle is chaotic and humans should build systems that are build on top of this natural disorder. By attempting to define and control disorder you must create so many convoluted rules (Like the leap day rule). Our calendar is an example of the human desire to "fix" nature to our own way of life instead of leaning to coexist with the natural disorderly processes that govern our lives. It's the same mindset that gives us the blatant disregard for the natural resources or climate.
This is a rather anarchic position but that's because I cannot help but inject anarchic rhetoric into my thought process due to so much of the way we live has been in blatantly build using archic concepts, even the calendar is dripping with it.
¹: Accidentally called it solstice sense I forgot there's a different word.
The 365.2422 days per celestial year is a math error we can fix.
We need to adjust the length of days and seconds but we can get rid of it completely if we wanted to.
It's not like noon means the maximum of the suns arc or sunset and sunrise don't already shift throughout the year.
The only thing that stops it is the momentum of a human measurement error.
If we use 366 we just get slightly shorter days by about 3 minutes. All of these time measurements are more arbitrary than feet and inches. Science back filled the bullshit with physical constants and there is no reason we cannot tie a proper system into alternative physics constants.
A year is a rotation of seasons. It has nothing to do with the day-night cycle. That should absolutely be separate.
And the 365.2422 isn't a math error. It's a mathematic ratio, rotation around the sun / rotation around itself. and it should absolutely be upheld.
The mathematical error os not basing our time counting on that ratio. The number is only 365.2422 because our second, hours, days are too long/short.
We can just decide we want one rotation to be exactly 366 units and then work backwards from there to determine new units.
Because I don't really have anything better to do today I made a JS generator for this calendar: https://codeberg.org/anaVal/misc/src/branch/main/cal.
Here is the full year 1 I generated using it:
Interestingly the 1st days of the 4th quarters are quite close to the starts of Gregorian months (June 1st, September 2nd, Dec 5th, March 4th).
Excellent calendar idea, excellent post. What do you think about using solar noon instead of time zones?
If you like the idea you'll probably appreciate the comment I just left were I made a program to generate it.
Time zones are complicated. One one side I like them because 12 is always noon which means you can get used to the sunset times. On the other hand I think the time shouldn't be related to sunrise at all and everyone should use UTC (or equivalent). Let sunrise and sunset be their own thing. Again let's not try and contain nature but instead define a simple method and just use that. Let the natural world tick according to it's own clock. We have our own atomic ones.
This also brings me to the idea that we should just use a single clock. Take an atomic clock, make it start counting and build all timekeeping around it. Basically the same thing computers are doing but for everyone. Let Sunrise, Noon, Year all be it's own thing and have a single timestamp for most timekeeping. Due to liking base6 I'd advocate for this timestamp to be in base6 instead of base10. By using it we are going to get an intuition of how much some length of time is that is separate from days.