An Actual Surprise

The holy war of operating systems, visualized as an IQ bell curve. The average devs (middle of the curve) are crying about needing Linux for coding. Meanwhile, both the "too simple to know better" folks and the enlightened geniuses have transcended the debate entirely—one thinks OS doesn't matter, and the other has ascended to some mythical "Temple OS" plane of existence. It's the perfect illustration of programming tribalism. After 15 years in the industry, I've watched countless junior devs have existential meltdowns over OS choice while the seniors just use whatever gets the job done. And then there's that one architect who built their own custom Gentoo setup that nobody else can comprehend.

Content Srigi srigi "Latency Numbers Every Programmer Should Know" It is hard for humans to get the picture until you translate it to "human numbers". 1 CPU cycle Level 1 cache access Level 2 cache access Level 3 cache access Main memory access Solid-state disk O Rotational disk IO Internet: SF to NYC Internet: SF to UK Internet: SF to Australia OS virtualization reboot SCSI command time-out Hardware virtualization reboot Physical system reboot 0.3 ns 1 s 0.9 ns 35 2.8 ns 9 s 12.9 ns 43 s 120 ns 6 min 50-150 us 2-6 days 1-10 ms 1-12 months 40 ms 81 Ms 4 years 8 years 183 ms 19 years 4 s 30 s 40 s 423 years 3000 years 4000 years 5 m 32 millenia

Ah, the legendary CrystalDiskInfo67.exe – that sketchy-looking executable with a CD icon that somehow ends up being more trustworthy than half your company's codebase. When your disk is making sounds like a blender full of paperclips, this is the hero you reluctantly download, hovering over the "Run Anyway" button while whispering "please don't steal my Bitcoin." The irony is that legitimate disk diagnostic tools often look more suspicious than actual malware. Trust issues? In this industry, we call that "experience."

The evolution of RAM-hungry applications, illustrated by increasingly fancy Winnie the Pooh: First, we blame Windows for hogging our RAM. Then Chrome enters the chat with its tab-per-gigabyte appetite. Discord slides in with its "simple chat app" that somehow needs more resources than early space missions. Firefox joins the party pretending to be the lightweight alternative while silently devouring your memory. And then there's Visual Studio 2022 – the final boss of RAM consumption. The IDE that makes you question if you really need both kidneys or if selling one for more RAM might be a sensible career investment. The real joke? We keep buying more RAM instead of demanding better software. Stockholm syndrome, developer edition.

The AUDACITY of Windows demanding not just one but THREE separate actions to fix literally ANYTHING! 💅 Left side: What normal humans expect - a simple update and shutdown. Right side: Windows being the high-maintenance drama queen it truly is - "No honey, I need you to update, AND THEN update again, AND THEN restart because apparently I can't figure out how to do all this in one step!" The absolute TRAUMA of waiting through multiple reboots while your deadline approaches. And we just take it! Stockholm syndrome at its finest!

Content Windows: has a complex and graceful shutdown process to make sure programs close correctly Linux: