Not that I endorse this in general but I was personally so busy heads down with work I had no idea about any of this until it came and went. It did not affect any of our companies (directly) when it happened so it never came up on my radar. Having said that, as a routine policy I do tend to explicitly ignore things because it’s easy to get caught up in all this. At the end of the day these are silly YouTube videos that are, let’s face it, cruising for attention and clicks. They’ll latch onto anything anytime because that’s the hit their audiences crave. The salient point is that will continue happening regardless of this brief note, which empirically is what has been driving my disengagement rather than attempting to “set the record straight” which I think is a moot point.
I assume the author is mainly referring to the video by Dave's Garage [1], at least the items listed match up pretty well with the points made in the video.
I seem to remember Dave making some of these points as examples rather than asserting them as the truth of what occurred with CrowdStrike, but it's been a couple days since I watched the video.
I was going to say, Dave did a great job covering the issue, despite the fact that he hasn't worked on Windows kernel for a lot time (10y+, if not for 20y+).
But in general, there is a lot of "parroting" going on from people who know very little or specialists in this field.
Spreading incorrect technical information about a trending current event to possibly millions of people or more just because the grift is hot and you want a quick buck is a bad thing, actually, and should be discouraged to whatever extent possible.
