this post was submitted on 07 Aug 2026
332 points (96.4% liked)
memes
22244 readers
2623 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads/AI Slop
No advertisements or spam. This is an instance rule and the only way to live. We also consider AI slop to be spam in this community and is subject to removal.
A collection of some classic Lemmy memes for your enjoyment
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It wasn't always like this.
I swear every version of Windows between 3.11 and XP was 100% reliable. Then it just started... slipping.
What's weird is that it often works on the second try.
If you’ve ever looked at windows desktop application source code (shudder) they have all this wacky shit around event handling in their native C/C++ APIs, which is a lot less clean that what you typically see in other languages / platforms which do similar event handling. It wouldn’t surprise me if that shit is hacky and buggy as fuck on the OS side of that implementation too.
So this would be your ctrl-c press event, and whatever handler code.
Though it’s been like 20 years since I looked at some of this. Maybe it’s better now, but somehow I doubt it.
Microsoft screwing up something as simple as an event listener is peak Microsoft