this post was submitted on 02 Nov 2025
1172 points (98.5% liked)

Programmer Humor

27412 readers
2482 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 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] FauxLiving@lemmy.world 39 points 2 weeks ago* (last edited 2 weeks ago) (4 children)

Kids these days with their 5% overclocks.

Back in my day we had 100% overclocks!

[โ€“] Pogbom@lemmy.world 21 points 2 weeks ago (2 children)

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 2 weeks ago (1 children)

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

[โ€“] tiramichu@sh.itjust.works 22 points 2 weeks ago (2 children)

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 2 weeks ago (1 children)

...we had finally achieved permanent turbo.

[โ€“] a_postmodern_hat@lemmy.world 3 points 2 weeks ago (1 children)
[โ€“] tomiant@programming.dev 2 points 2 weeks ago

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

[โ€“] Klear@quokk.au 1 points 2 weeks 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 2 weeks ago (2 children)

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.

[โ€“] Evoliddaw@lemmy.ca 2 points 2 weeks ago

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

I am. I am a greybeard.

[โ€“] tomiant@programming.dev 2 points 2 weeks ago

A 486DX with the J20 jumper set! HAH!

[โ€“] psud@aussie.zone 3 points 2 weeks ago (1 children)

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 2 weeks ago (1 children)

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

[โ€“] psud@aussie.zone 2 points 1 week ago (1 children)

It was the wondrous system "DOS 6.2"

[โ€“] FauxLiving@lemmy.world 1 points 1 week ago (1 children)

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

[โ€“] psud@aussie.zone 1 points 1 week ago

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

[โ€“] mrmanager@lemmy.today 3 points 2 weeks ago

This brings out nostalgia...

66 MILES PER HOUR!