1254
submitted 11 months ago* (last edited 11 months ago) by Bring_Back_Buggy_Whips@sh.itjust.works to c/programmer_humor@programming.dev
you are viewing a single comment's thread
view the rest of the comments
[-] FauxLiving@lemmy.world 42 points 11 months ago* (last edited 11 months ago)

Kids these days with their 5% overclocks.

Back in my day we had 100% overclocks!

[-] Pogbom@lemmy.world 23 points 11 months ago

You might have meant it as a joke but just in case someone else isn't aware, this button actually made your CPU slower 🤓

[-] ZILtoid1991@lemmy.world 9 points 11 months ago

Depends on the motherboard version. On later ones, the turbo actually worked to make your PC faster.

[-] tiramichu@sh.itjust.works 22 points 11 months ago

As far as I understand, it's purely marketing semantics.

The point of the 'Turbo' button is to slow the CPU down to provide compatibility with old software that was written with a fixed clockspeed, where the software would become unusably fast on newer CPUs.

Calling this a "slow" mode or "compatibility" mode wasn't very marketing-sexy however, so manufacturers just flipped it around and called the normal speed 'Turbo'.

With later systems, developers all became aware that varying CPU frequencies were a thing, and started to base their software timings on the realtime clock instead.

So in later systems there was no longer any need to have the CPU run at anything other than its maximum (normal) speed - and the turbo button simply went away.

[-] tomiant@programming.dev 5 points 11 months ago

...we had finally achieved permanent turbo.

[-] a_postmodern_hat@lemmy.world 3 points 11 months ago
[-] tomiant@programming.dev 2 points 10 months ago

"We called it Purbo. It didn't catch on."

[-] Klear@quokk.au 1 points 10 months ago

With later systems, developers all became aware that varying CPU frequencies were a thing, and started to base their software timings on the realtime clock instead.

If only. Not sure how common it is nawadays - definitely still happening on occasion, but for example GTA: Vice City's physics get screwed up with uncapped framerate.

[-] FauxLiving@lemmy.world 5 points 11 months ago

You might have meant it as a joke

Yeah, I didn't think anyone would get the joke if I posted a picture of a 486DX with the J20 jumper set. You have to be a greybeard to remember that.

[-] tomiant@programming.dev 2 points 11 months ago

A 486DX with the J20 jumper set! HAH!

[-] Evoliddaw@lemmy.ca 2 points 11 months ago

My first thought was "hey I'm not a greybeard"

I am. I am a greybeard.

[-] psud@aussie.zone 3 points 10 months ago

Turbo bumped my 8MHz 386 to sixteen megahertz

It never got switched off, except in some games that a slower CPU made easier (some games back then ran just as fast as the hardware could run them, expecting the computers or turn to be the state of the art) By the time of the machine in the picture unturbo wasn't enough so we used a TSR* program called goSlow to get specific performance

*Terminate, Stay Resident; a program that could run in the background

[-] FauxLiving@lemmy.world 1 points 10 months ago

Run in the background? Look at you with your fancy multitasking OS

[-] psud@aussie.zone 2 points 10 months ago

It was the wondrous system "DOS 6.2"

[-] FauxLiving@lemmy.world 1 points 10 months ago

Doesn't that require Extended memory? I don't think that's going to catch on

[-] psud@aussie.zone 1 points 10 months ago

It did, extended memory came about the same time we needed to show down the system

[-] mrmanager@lemmy.today 3 points 11 months ago

This brings out nostalgia...

[-] cupcakezealot@piefed.blahaj.zone 3 points 10 months ago

66 MILES PER HOUR!

this post was submitted on 02 Nov 2025
1254 points (98.6% liked)

Programmer Humor

33385 readers
1239 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 3 years ago
MODERATORS