You don't have to be a diversity hire to write a null pointer dereference in a C/C++ program. Even the best of us do it.
This event reminds me of the crash of the AT&T phone system on January 15, 1990, also caused by a bug in a C program, though not the same kind of bug. You can't blame that one on DEI. The frightening truth is that some …
You don't have to be a diversity hire to write a null pointer dereference in a C/C++ program. Even the best of us do it.
This event reminds me of the crash of the AT&T phone system on January 15, 1990, also caused by a bug in a C program, though not the same kind of bug. You can't blame that one on DEI. The frightening truth is that some systems we depend on are remarkably fragile ín certain ways.
Anyway, the real problem here, I believe as a cybersecurity expert, is the widespread use of the Microsoft Windows operating system for infrastructure purposes. It's a desktop OS that was not designed for use in servers; keeping it secure requires frequent patching, and every patch is an opportunity for something to go wrong. Linux would be a better choice for many purposes.
I agree that Microsoft never really caught up with Unix (Linux) or any other OS (are there any others?) specifically built for "mainframe" - or corporate - uses. Who got these companies to go with Microsoft? A LOT of businesses use Linux in their servers, etc.
It's not just Microsoft cloud servers that were affected, when I see the reported blue screens at airports these are windows machines designed for end user interaction, many running in a type of locked down "kiosk" mode. I use windows every day and were not affected by this. I think this is purely on CrowdStrike (and whoever chose to use CrowdStrike) and is not a Microsoft problem. See my separate comment on that topic.
You don't have to be a diversity hire to write a null pointer dereference in a C/C++ program. Even the best of us do it.
This event reminds me of the crash of the AT&T phone system on January 15, 1990, also caused by a bug in a C program, though not the same kind of bug. You can't blame that one on DEI. The frightening truth is that some systems we depend on are remarkably fragile ín certain ways.
Anyway, the real problem here, I believe as a cybersecurity expert, is the widespread use of the Microsoft Windows operating system for infrastructure purposes. It's a desktop OS that was not designed for use in servers; keeping it secure requires frequent patching, and every patch is an opportunity for something to go wrong. Linux would be a better choice for many purposes.
I agree that Microsoft never really caught up with Unix (Linux) or any other OS (are there any others?) specifically built for "mainframe" - or corporate - uses. Who got these companies to go with Microsoft? A LOT of businesses use Linux in their servers, etc.
It's not just Microsoft cloud servers that were affected, when I see the reported blue screens at airports these are windows machines designed for end user interaction, many running in a type of locked down "kiosk" mode. I use windows every day and were not affected by this. I think this is purely on CrowdStrike (and whoever chose to use CrowdStrike) and is not a Microsoft problem. See my separate comment on that topic.