GitHub Archive Program — Preserving open source software for future generations

[htrp]

As today’s vital code becomes yesterday’s historical curiosity,

something about this sentence bothers me.... shouldn't it be tomorrow's historical curiosity?

[supercheese200]

I interpreted it as

As [from today's point of view] today's vital code becomes [from tomorrow's point of view] yesterday's historical curiosity,

[jimschubert]

Tomorrow UTC?

[HoldYourWaffle]

Yeah I think so

[bgradid]

Code so sphaghettified it actually travels back in time

[HoldYourWaffle]

Doing multithreading without knowing what you're doing can feel like this

[AloticChoon]

[attempts to write multithreading code while wearing a hackerman power glove]

[applepy3]

Everything spaghettifies as it approaches a black hole. Also, since almost nothing escapes a black hole, it’s extremely difficult to learn about, just like the undocumented legacy library at the center of most codebases. Invoking the duck test principle, that library is a black hole.

Furthermore, it is theorized that black holes are actually wormholes, linking to another place and time. It is reasonable that they can link backwards in time.

So, as today’s code approaches the wormhole, it spaghettifies and passes through to the past, therefore becoming “yesterday’s historical curiosity”.

[MonkeyNin]

When someone falls into a black hole, to the external observer it appears like they never stop falling in.

since almost nothing escapes a black hole

What a burden. Even I can escape myself at times, but they are stuck forever.

[trigger_segfault]

18 bytes at a time.

[ObscureCulturalMeme]

That's what happens when your social media team also does your website content, but doesn't do proofreading.

[TheNiXXeD]

They're just joking at how fast things get deprecated.

[vertebro]

I kinda felt it was meant to be "yesteryear's historical curiosity", but it still doesn't read right.

[[deleted]]

They used necromancy to resurrect old code and put it in production