Collection of Lame Jokes

  • Thread starter Thread starter quddusaliquddus
  • Start date Start date
  • Tags Tags
    Jokes
Click For Summary
The discussion revolves around sharing and enjoying "lame" jokes, with participants contributing various puns and one-liners. Jokes include classic setups like "A duck walks into a pharmacy..." and "Why did the chicken cross the road?" along with playful wordplay, such as "What do you call a boomerang that doesn't work? A stick." The humor is characterized by its groan-inducing quality, with many jokes eliciting laughter despite their simplicity. Participants also engage in light banter about the nature of humor, with some jokes being deemed too funny to qualify as "lame." The thread highlights a shared enjoyment of corny humor and the camaraderie that comes from exchanging jokes, creating a lighthearted atmosphere.
  • #23,351
Who's got nostalgia for Y2K?

IMG_1555.webp


Of course, nobody on the Internet knew he was a dog until the book outed him!
 
Last edited:
  • Like
Likes collinsmark
Physics news on Phys.org
  • #23,352
jtbell said:
Who's got nostalgia for Y2K?

View attachment 366960

Of course, nobody on the Internet knew he was a dog until the book outed him!
And no one knew toilet paper was going to run until 2020...
 
  • #23,353
jtbell said:
Who's got nostalgia for Y2K?

View attachment 366960

Of course, nobody on the Internet knew he was a dog until the book outed him!

I know (or at least strongly suspect) that Y2K problems isn't the real issue here. Nevertheless, I remember being issued with a bunch of paper, the thickness of several telephones books (anyone know what a telephone book is anymore?), with C code, in small font on both pages, being asked if I would please use my free time to scan through it and see if there should be any problems.

I mean why on paper? And my free time?!

I'm glad I'm retired.
 
  • #23,354
sbrothy said:
I know (or at least strongly suspect) that Y2K problems isn't the real issue here. Nevertheless, I remember being issued with a bunch of paper, the thickness of several telephones books (anyone know what a telephone book is anymore?), with C code, in small font on both pages, being asked if I would please use my free time to scan through it and see if there should be any problems.

I mean why on paper? And my free time?!

I'm glad I'm retired.
You scanned toilet paper?
 
  • #23,355
WWGD said:
You scanned toilet paper?
It might as well have been.
 
  • Haha
  • Like
Likes jack action and collinsmark
  • #23,356
sbrothy said:
It might as well have been.
I just used the same solution for Y2K, that we used for Y1K.
 
  • #23,357
The moon landing conspiracies are back again thanks to Kim Kardashian.

Pure lunacy!
 
  • #23,358
Ivan Seeking said:
I just used the same solution for Y2K, that we used for Y1K.
The Euro was introduced in 1998 here. That meant a lot of examination of very, very old mainframe code in banking software, esp. as notations were swapped from the price of one dollar to the price of one euro. Checking the Y2K problem was a byproduct. I had never imagined seeing real-life assembler code before, but I did. At least it gave me the rare opportunity to watch Sylvester fireworks at the 21st level over the town.
 
  • #23,359
fresh_42 said:
The Euro was introduced in 1998 here. That meant a lot of examination of very, very old mainframe code in banking software, esp. as notations were swapped from the price of one dollar to the price of one euro. Checking the Y2K problem was a byproduct. I had never imagined seeing real-life assembler code before, but I did. At least it gave me the rare opportunity to watch Sylvester fireworks at the 21st level over the town.
Only announced much later, we did have a Y2K related national defense system fail

This is from Google AI, but I remember when this information was released, which is how I knew to look it up.

One significant US defensive system experienced a failure shortly after midnight UTC on January 1, 2000 (which was still Dec 31st, 1999, in the US time zones). A ground-based computer failure temporarily blinded several US spy satellites.

The system, an intelligence processing station at Fort Belvoir, Virginia, went offline for two to three hours. The problem wasn't with the satellites themselves, which remained under control, but with the ground station's ability to process the incoming information due to a Y2K-related error in a software patch.
 

Similar threads

Replies
449
Views
32K
Replies
57
Views
8K
Replies
3
Views
137
9
Replies
401
Views
39K
Replies
7
Views
3K
Replies
1
Views
3K
Replies
185
Views
10K
Back
Top