Yes, seems like a silly opinion to me. If your system breaks upon seeing a deprecation warning (which... It shouldn't?), you can work around it by filtering or

Yes, seems like a silly opinion to me. If your system breaks upon seeing a deprecation warning (which... It shouldn't?), you can work around it by filtering or whatever, and have the remaining deprecation period to actually fix it. If your system breaks because you failed to notice the warning and the feature was actually removed, you have no choice but to actually fix it, under time pressure. So even if it "might as well be a fatal error", at least it's a fatal error that's more likely to be manageable instead of a fire.