Ordering the same old Windows-crash and Arch-brag memes at the Krusty Krab
Description
Six-panel SpongeBob scene: a teal fish customer faces cashier Squidward behind the Krusty Krab counter. Panel 1 shows the fish saying, “I’ll have a…”. Panel 2 continues with overlaid text: “"Windows blue screen in public" picture,”. Panel 3 the fish adds: “"Updating windows meme"”. In panel 4 Squidward frowns, captioned “How original”. Panel 5 the fish finishes: “and one "I use arch btw"”. Panel 6 Squidward, now smirking, responds, “Daring today, aren’t we”. The meme jokes about the developer community repeatedly recycling three cliché operating-system jokes: photos of public BSODs, Windows-update rage, and Linux users flexing that they use Arch. It highlights OS culture wars, predictable bug humor about crashes, and tired yet enduring dev-community meme formats
Comments
54Comment deleted
Dev forums have memoized BSOD photos, Windows-update rants, and “I use Arch btw” so hard that we’ve rediscovered the three classic problems in CS: cache invalidation, naming things, and coming up with a fourth OS joke
After 20 years in tech, you realize the real blue screen of death is watching junior devs discover Docker for the first time and immediately suggesting we containerize the legacy COBOL system that's been running flawlessly since 1987
The real irony here is that by the time you finish explaining why your Arch setup is superior, the Windows machine has already blue-screened twice, auto-updated, rebooted, and is now asking if you want to set up Cortana - while your Arch system is still compiling dependencies for a text editor you installed three hours ago
Public BSOD, forced update, and 'I use Arch, btw' - the CAP theorem of dev memes: choose any two and you still lose originality
BSOD selfies and Arch flexes: the dev equivalent of a 15-year vet still fighting DLL hell while LARPing as a kernel whisperer
BSOD in public, Windows updating mid-demo, and “I use Arch btw” - three punchlines to the same root cause: your CAB is a calendar invite nobody attends
Welcome to linux community, where we laugh at the same 6 jokes Comment deleted
windows FS performance windows' memory footprint windows' syscalls CPU footprint windows' respect for privacy windows' uptime windows' CPU scheduler Comment deleted
I actually have little information on how good is NTFS' performance compared to ext4 or btrfs Comment deleted
not easy to compare. Neanderthal Technology File Shredder aka NTFS sucks anyways. Comment deleted
neanderthal technology file shredder lmao Comment deleted
I believe it's less about the specific file systems & more about linux just being really fucking good at handling them. Something about nodes and stuff, I'm not really an expert on this topic. Comment deleted
what's the seventh? Comment deleted
i might forget it because i code when stressed...... Comment deleted
inodes Comment deleted
that Comment deleted
linux filesystems do be having permissions tho Comment deleted
I think windows has too ? Comment deleted
very primitive Comment deleted
isn't it more complicated than linux's one? Comment deleted
my understanding of it is you have to enter in an admin password to access files outside of your user directory Comment deleted
it's more than that afaik. It has a similar structure to linux's permissions, except there isn't an owner, but a list of users that can access it, with write-read-execute set per user. Comment deleted
don't quote me on that though Comment deleted
ahh i see Comment deleted
and windows also has some builtin system protection from the user, so you get warned before deleting system32, and can't delete some other stuff at all (even with administrator rights) Comment deleted
actually, files can be owned by either a user or a group. Comment deleted
you cannot imagine how wrong you are Comment deleted
jokes on you i can Comment deleted
$ /bin/echo 'you are wrong' > /tmp/meh Comment deleted
using /bin/ to call a binary is haram Comment deleted
it shows you can indeed access files outside your homedir Comment deleted
still haram Comment deleted
/dev/sda "you are wrong" Comment deleted
…that doesn't even do anything Comment deleted
it does if you dd your echo onto your /dev/sda beforehand Comment deleted
I believe that's impossible. Comment deleted
hold on imma try it Comment deleted
it is, iff the random data happens to be equal to the contents of your disk Comment deleted
I got that part, I just think you can't just write data to disk by writing to /dev/sda Comment deleted
i'm gonna do it Comment deleted
sduo Comment deleted
nvm Comment deleted
oh Comment deleted
next step: installing windows Comment deleted
WOW I liked that joke a lot... Of course, that dd command has chances of leaving the disk unmodified, if you're so lucky that dd reads from urandom exactly the same bit string that your disk has written in the surface. Assuming urandom is a perfect random number generator (which is not), then your chances are 0.5 to the power of the number of bits you read and wrote Comment deleted
/dev/sda: Permission denied Comment deleted
look, it works on my machine Comment deleted
complicate, yes. wouldn't call it primitive tho. they look more like a NFS4 ACL. Comment deleted
Well just checked, files have owners, you can add rights to all admins, system and specified users Comment deleted
on ntfs everything shows up as rwxrwxrwx Comment deleted
its not built in to the filesystem, its just the operating system Comment deleted
unless theres something i dont know about, its not like i use windows actively lol Comment deleted
i wonder why linux always sees files on ntfs filesystems as rwxrwxrwx then... Comment deleted
lol Comment deleted