this post was submitted on 19 Jul 2024
63 points (100.0% liked)
Technology
37711 readers
155 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I don't disagree, but today the blame lies with CrowdStrike, not Windows. As much as I hate defending Windows.
I've seen a weird number of people blaming Microsoft for this today, and an even weirder number of people making fun of people saying this isn't on Microsoft
Microsoft chose to work with these people and accepted their faulty input. How is it not Microsoft's fault?
If you had a Samsung fridge, and you willingly put a bomb in the fridge, would you blame Samsung when your fridge explodes?
Microsoft gives you the freedom to install software that runs with the same level of privilege as the kernel itself. You're the one that chose to install defective software, and then give it kernel level permissions. You put a bomb in your computer and now you're blaming Microsoft after the bomb exploded.
Microsoft didn't make the decision to allow the faulty input, the person who installed the software did, when they gave it permission to run in kernel mode.