this post was submitted on 05 Dec 2023
465 points (98.5% liked)

internet funeral

6808 readers
3 users here now

ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤart of the internet

What is this place?

!hmmm@lemmy.world with text and titles

• post obscure and surreal art with text

• nothing memetic, nothing boring

• unique textural art images

• Post only images or gifs (except for meta posts)

Guidlines

• no video posts are allowed

• No memes. Not even surreal ones. Post your memes on !surrealmemes@sh.itjust.works instead

• If your submission can be posted to !hmmm@lemmy.world (I.e. no text images), It should be posted there instead

This is a curated magazine. Post anything and everything. It will either stay up or be lost into the void.

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] Littleborat@feddit.de 11 points 9 months ago (1 children)

I remember using win 3.11 and my dad would tell me to close windows I am not using so the machine does not grind to a halt. Good times. Windows could to nothing back then. Minesweeper maybe.

[–] Thrashy@lemmy.world 6 points 9 months ago

Before Win95/NT, Windows was basically just a skin on top of DOS, and DOS had never been designed with multitasking in mind. That meant that (with some exceptions, like 8-bit DOS programs running in virtual 8086 mode on a 386) for multiple programs to play nice with each other within the GUI, they had to "cooperatively multitask," that is, they had to be programmed to share a common memory address space, and to yield back control of the processor to Windows periodically, so that the other open programs could get some execution cycles in before they had to yield in turn. As you can imagine, this didn't work particularly well in practice, with software commonly forgetting to yield back to the task scheduler and pooping all over shared memory on a regular basis. Windows 95 was a quantum leap forward, with preemptive multitasking and independent address space for each running process.