Actually lot less than the browser. Under 300MB, I just checked, and that's mostly just the network buffer which is 150MB by default.

Sound typically (*) didn't require "drivers" or any TSR though. The game had to do all the hardware control itself.

It was usually enough to set a BLASTER variable to point it at the correct IRQ, DMA and memory address, and perhaps run a program at boot to initialize the card and set volume levels, but no TSR eating up memory.

(*) Some exceptions are later soundcards of the Win 9x era that did crappy emulation of a real Soundblaster via a TSR in DOS.

Ah the sweet sounds of a simpler, worryfree time ...

The point is that your example use case of "YouTube 4k videos" doesn't need a browser full of bloated js garbage.

Just don’t compain that YouTube doesn’t play 4K videos anymore.

strange, mpv handles it just fine

I remember when I got my first computer with 1GB of RAM, where my previous computer had 64MB, later upgraded to 192MB. And there were only like 3 or 4 years in between them.

It was like: holy shit, now I can put all the things in RAM. I will never run out.

most PCs by that time had built-in MIDI synthesizers

Built-in? You had AdLib cards for FM synthesis, but they were never built-in and most PCs didn't even have them. Adlib cards used the Yamaha OPL2 or OPL3 chip.

Along came Creative Labs with their AWE32, a synthesizer card that used wavetable synthesis instead of FM

You are skipping a very important part here: cards that could output digital audio. The early Soundblaster cards were pioneers here (SB 1.0, SB 2.0, SB Pro, SB16). The SB16 for example was waaaaay more popular than the AWE32 ever was, even if it still used OPL3 based FM synth for music. It's the reason why most soundcards in the 90s were "Soundblaster compatible".

Digital audio meant that you could have recorded digital sound effects in games. So when you fired the shotgun in Doom to kill demons, it would play actual sound effects of shotgun blasts and demon grunts instead of bleeps or something synthesized and it was awesome. This was the gamechanger that made soundcards popular, not wavetable.

The wavetable cards I feel were more of a sideshow. They were interesting, and a nice upgrade, especially if you composed music. They never really took off though and they soon became obsolete as games switched from MIDI based audio to digital audio, for example Quake 1 already had its music on audio tracks on CD-ROM, making wavetable synthesis irrelevant.

BTW, I also feel like you are selling FM synthesis short. The OPL chips kinda sucked for plain MIDI, especially with the Windows drivers, and they were never good at reproducing instrument sounds but if you knew how to program them and treated the chip as its own instrument rather than a tool to emulate real world instruments, they were capable of producing beautiful electronic music with a very typical sound signature. You should check out some of the adlib trackers, like AdTrack2 for some examples. Many games also had beautiful FM synthesized soundtracks, and I often preferred it over the AWE32 wavetable version (e.g. Doom, Descent, Dune)

Yeah god forbid people have some interesting discussion on this platform, right?

Good news ... it's a suppository!

I've found that the silliest desktop problems are usually the hardest to solve, and the "serious" linux system errors are the easiest.

System doesn't boot? Look at error message, boot from a rescue disk, mount root filesystem and fix what you did wrong.

Wrong mouse cursor theme in some Plasma applications, ignoring your settings? Some weird font rendering issue? Bang your head against a wall exploring various dotfiles and rc files in your home directory for two weeks, and eventually give up and nuke your profile and reconfigure your whole desktop from scratch.

People be like:

This is not a chrome vs firefox issue. People using an adblocker on firefox are getting blocked just the same.

See:

source (sorry for the reddit link)