this post was submitted on 19 Jul 2024
1203 points (99.5% liked)
Technology
58737 readers
4552 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Probably because it's a Crowdstrike issue, they've pushed a bad update.
OK, but people aren't running Crowdstrike OS. They're running Microsoft Windows.
I think that some responsibility should lie with Microsoft - to create an OS that
I get that there can be unforeseeable bugs, I'm a programmer of over two decades myself. But there are also steps you can take to strengthen your code, and as a Windows user it feels more like their resources are focused on random new shit no one wants instead of on the core stability and reliability of the system.
It seems to be like third party updates have a lot of control/influence over the OS and that's all well and good, but the equivalent of a "Try and Catch" is what they needed here and yet nothing seems to be in place. The OS just boot loops.
It's not just Windows, it's affecting services that people that primarily use other OS's rely on, like Outlook or Federated login.
In these situations, blame isn't a thing, because everyone knows that a LSE can happen to anyone at any time. The second you start to throw stones, people will throw them back when something inevitably goes wrong.
While I do fundamentally agree with you, and believe that the correct outcome should be "how do we improve things so that this never happens again", it's hard to attach blame to Microsoft when they're the ones that have to triage and ensure that communication is met.
I reckon it's hard to attach blame to Microsoft because of the culture of corporate governance and how decisions are made (without experts).
Tech has become a bunch of walled gardens with absolute secrecy over minor nothings. After 1-2 decades of that, we have a generation of professionals who have no idea how anything works and need to sign up for $5 a month phone app / cloud services just to do basic stuff they could normally do on their own on a PC - they just don't know how or how to put the pieces together due to inexperience / lack of exposure.
Whether it's corporate or government leadership, the lack of understanding of basics in tech is now a liability. It's allowed corporations like Microsoft to set their own quality standards without any outside regulation while they are entrusted with vital infrastructure and to provide technical advisory, even though they have a clear vested interest there.