Hacker News Reader

Yep. I'll admit I've acted faster to hard set dates than some "in the future" message. I've also seen some tools become really noisy about deprecation spanning many lines AND repeating. Please don't log the same message over and over for each instance. Color or add emoji if you must to grab attention, but once is enough. It's annoying when you can't do anything about it at that time and have to sift through this extra noise when hunting down another issue in the CI log. Add a link that goes over it in more detail and how to migrate for that specific deprecation.

I don't think that was a serious suggestion, the article says it is sarcasm near the end.

But yes, that would be the worst idea ever.

Random is bad, but scheduled windows of breakage is good.