this post was submitted on 17 Mar 2024
81 points (100.0% liked)

Science Memes

20690 readers
1859 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.



Meta Post Tags



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.


If you are here asking: "Is this a science meme?"

Probably, yes. We use the Dawkins definition of meme: a replicating idea, not just an image macro with a fact on it. A good post here doesn't need to teach you something. It needs to make you ask something: who, what, where, when, and especially why or how.

Science isn't a filing cabinet of facts, it's a conversation. For example, a photo of an eel or other localized wildlife counts because most people never see one, and wonder is the first step of inquiry. A car meme counts if it makes you curious about what's under the bonnet. If you want to talk about something you noticed in the world, chances are someone else wants to talk about it too.

We moderate for vibe, not category. Pruning is light, especially where a post creates interesting discussion. Experimenting is encouraged.

See the pinned paper on Shitposting as Public Pedagogy if you want the academic case for why this works.



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 3 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] Tranus@programming.dev 0 points 2 years ago (4 children)

Y2K specifically makes no sense though. Any reasonable way of storing a year would use a binary integer of some length (especially when you want to use as little memory as possible). The same goes for manipulations; they are faster, more memory efficient, and easier to implement in binary. With an 8-bit signed integer counting from 1900, the concerning overflows would occur in 2028, not 2000. A base 10 representation would require at least 8 bits to store a two digit number anyway. There is no advantage to a base 10 representation, and there never has been. For Y2K to have been anything more significant than a text formatting issue, a whole lot of programmers would have had to go out of their way to be really, really bad at their jobs. Also, usage of dates beyond 2000 would have increased gradually for decades leading up to it, so the idea it would be any sort of sudden catastrophe is absurd.

[–] frezik@midwest.social 1 points 2 years ago

With an 8-bit signed integer counting from 1900...

Some of the computers in question predate standardizing on 8 bits to the byte. You've got a whole post here of bad assumptions about how things worked.

[–] SkippingRelax@lemmy.world 1 points 2 years ago

a whole lot of programmers would have had to go out of their way to be really, really bad at their jobs.

You don't spend much time around them, do you?

[–] TheOctonaut@mander.xyz 1 points 2 years ago (1 children)

The issue wasn't using the dates. The issue was the computer believing it was now on those dates.

I'm going to assume you aren't old enough to remember, but the "only two digits to represent the year" issue predates computers. Lots of paper forms just gave two digits. And a lot of early computer work was just digitising paper forms.

[–] Scrollone@feddit.it 2 points 2 years ago

I remember paper forms having "19__" in the year field. Good times

[–] breakingcups@lemmy.world 0 points 2 years ago

You do realize that "counting from 1900" meant storing only the last two digits and just hardcoding the programs to print"19" in front of it in those days? At best, an overflow would lead to 19100, 1910 or 1900, depending on the print routines.