261
top 23 comments
sorted by: hot top controversial new old
[-] psud@aussie.zone 27 points 1 day ago* (last edited 1 day ago)

LibreOffice calc has

  • 0 = 1899-12-30,
  • 1= 1899-12-31,
  • 2=1900-01-01

I wonder if they were trying to one-up excel.

[-] MazonnaCara89@lemmy.ml 21 points 1 day ago

So, are these the so-called 0-days everybody talks about on windows and linux?

(This is a joke for everybody not getting it)

[-] Kushan@lemmy.world 26 points 1 day ago

I mean... They're all kind of arbitrary in their own way, but one could argue that the excel time being invalid is actually useful because it serves as a null value - you know it's incorrect, whereas on the other systems it could be the default date or it could be the actual date.

[-] DomeGuy@lemmy.world 45 points 1 day ago

If you think that's bad, look at what "1" means.

(And, honestly, at least windows' "last big calendar change" and excel's "start of the century when we wrote it" are reasonable points. The unix "let's make it recent so we can fit an absurdly small unit as an integer!" Epoch is just... Weird.)

[-] bleistift2@sopuli.xyz 53 points 1 day ago* (last edited 1 day ago)

“start of the century when we wrote it”

This meme wouldn’t exist had they done that. But they chose the zeroeth, not the first, of January for Excel.

[-] radix@lemmy.world 26 points 1 day ago

Yep. "1" is 12:00am on 1-Jan-1900

Numbers less than zero just give a weird error. Between zero and less than one give a nonsense date-formatted non-date.

[-] homesweethomeMrL@lemmy.world 17 points 1 day ago

Fucking Microsoft.

[-] rumba@lemmy.zip 14 points 1 day ago

Now do 03:14:08 UTC on 19 January 2038!

[-] psud@aussie.zone 4 points 1 day ago

I think we're mostly using 64 bit machines now. Even loads of embedded stuff is running on 64 bit processors now.

There will still be a lot of old software and hardware that needs updating before the 32 bit Unix time overflow

[-] rumba@lemmy.zip 2 points 17 hours ago

Hopefully it's another Y2K nothing burger. (Which was largely because a lot of people prepared for it)

[-] psud@aussie.zone 1 points 15 hours ago

Yeah, I got my first office job thanks to Y2K. An enormous amount was spent fixing it, with some of the fixes needed years before 2000-01-01, for example systems that projected into the future

Biggest problem I saw was a program that stored 1999 as 99 and displayed "19".year

So when set to January 2000 it showed 19100. Its calculations were fine, just its display and reports were wrong

[-] rumba@lemmy.zip 1 points 15 hours ago

Agreed, most of the actual problems seemed to be in reporting. I saw some cobol stuff that went to 1900. There were a few things where 00 wasn't an option, But mostly it was just really heinously written stuff that wasn't expected to be in service even in the '90s.

[-] codexarcanum@lemmy.dbzer0.com 5 points 1 day ago

I'd never noticed that in this order, it's almost π!

Off by 0.001 and some change; that coincidence is going to haunt me.

[-] rumba@lemmy.zip 3 points 1 day ago

the actual last 32 bit micro happens in 3:14:07 but that's the wrong way :)

[-] davidgro@lemmy.world 5 points 1 day ago

Easy. Just be 64-bit. (Or unsigned, but that's not as good.)

[-] codexarcanum@lemmy.dbzer0.com 7 points 1 day ago

🧐: 0 is the origin of time, the big bang (if you believe in that kind if thing)

The problem then is figuring out when earth (and then human) time starts, but we can just add some arbitrary offsets that feel right and everyone agrees on.

[-] felsiq@lemmy.zip 12 points 1 day ago

Time is a pain in the ass and unfortunately not this simple, since it’s affected by energy and doesn’t pass at constant rates. The amount of time that’s passed since the Big Bang is different on earth than it is on a neutron star, for example, so one fundamental reference time isn’t possible the way it is for other units.

[-] otacon239@lemmy.world 5 points 1 day ago* (last edited 1 day ago)

Listen. Let’s just do it simple. Everyone sync their clocks with mine right now. It says it’s 10:57 at the moment, but we’ll just subtract that in the future going forward. Ready? 3, 2, 1, Go! Now we know where 0 is, whew. Problem solved, scientists!

Edit: wait, now it says 10:58…

[-] driving_crooner@lemmy.eco.br 4 points 1 day ago

I work in the accounting team of my company, doing python development, and a lot of the sources I get came from the accountants that only use excel and every once in a while the date columns came completely fucked with that integral number excel uses sometimes and is a pain in the ass to translate to datetime.

[-] captain_aggravated@sh.itjust.works 4 points 1 day ago* (last edited 1 day ago)

January zeroth, 1900. A red letter date.

[-] Malfeasant@lemmy.world 3 points 1 day ago

On Linux, 0 often works out to 12/31/1969 after local time zone conversion...

[-] match@pawb.social 2 points 1 day ago

0 means now 🙂

this post was submitted on 01 Jul 2025
261 points (97.1% liked)

Science Memes

15505 readers
2789 users here now

Welcome to c/science_memes @ Mander.xyz!

A place for majestic STEMLORD peacocking, as well as memes about the realities of working in a lab.



Rules

  1. Don't throw mud. Behave like an intellectual and remember the human.
  2. Keep it rooted (on topic).
  3. No spam.
  4. Infographics welcome, get schooled.

This is a science community. We use the Dawkins definition of meme.



Research Committee

Other Mander Communities

Science and Research

Biology and Life Sciences

Physical Sciences

Humanities and Social Sciences

Practical and Applied Sciences

Memes

Miscellaneous

founded 2 years ago
MODERATORS