I've never seen anyone care as much for overtime as games journalists or internet personalities do when it comes to gaming. Heck, people doing overtime as doctors or truck drivers, where your life is at stake, never get this same type of attention (that's not to say that they shouldn't get more attention). It often just seems disingenuous and like they're more just stirring up shit or fellating developers, rather than concerns for work conditions.
It often ends up being made into a black or white issue "crunch vs no crunch", which just feels wrong. Perhaps the circumstances of crunch matter? That would be a way to consider the situation with a bit more nuance. Though I can't really expect nuance from Jim Sterling, as his schtick is kind of being the man on the soap box with a humoristic presentation relying on strawmen to build his arguments. And it's not like he hides that he often has no idea about projects and project management. Nor that he hides selectively believing whichever source confirms his point. Honestly, while I applaud his ideal of universalism, he often lacks the nuance to actually differentiates between degrees, either quantitatively or qualitatively, of something. If you lack that nuance, then killing an ant and killing a human is the same thing according to an universal view of killing, which is what I personally feel like Jim lacks in a lot of the things he brings up.
Personally the talk about crunch should be one of the circumstances. Are they paid and in what manner? Are they limited in scope or are someone just outright trying to run half a project as crunch? Was a delay considered and were it rejected due to various concerns, especially economic? Were a softer crunch periode considered, perhaps with voluntary overtime? Are exceptions taken when a person is clearly struggling under the overtime conditions? Are there any post-mortems, project evaluations, in order to realize what went wrong and what could be learnt for the next project in order to make the crunch period less intense or better? What means for stress relief are available for your developers? Etc.
That feels like a better conversation than running with pitchforks at the mention of crunch: "CRUNCH!? DIEEEE!!!! IT'S ALL THE BOSS' FAULT!!!". Or just saying "there must always be a crunch, there must always be a crunch, there must...". Yelling at one another is definitely not a conversation, neither is holding your ears while talking to someone. Which is why a conversation is likely to be far more fruitful than blanket positions.