The quiet way to kill a feature: let it get unreliable
Quote
there is a nice benefit you get by D stabilizing something within your own within your own ecosystem that you don't really care to maintain.
Episode 36: we're crawling on life away here. Maybe we are, maybe some other (approx., from transcript intro) 00:25:36 (play audio from this timestamp, opens in a new tab)
Voice-matched
Summary
Dave's 'IT guy' theory on Apple's API dropping feed URLs. Announcing you're cutting a feature others depend on brings the mob with pitchforks, which Apple doesn't want while facing antitrust scrutiny. Making it less reliable, or just not caring, gets the same result: once 15 to 20 percent of URLs go missing, everyone bails, and it can be dropped without an announcement.
Also said
Episode 36: we're crawling on life away here. Maybe we are, maybe some other (approx., from transcript intro) 00:27:07 (play audio from this timestamp, opens in a new tab)
you can either put in a feature that makes it less useful, or are less reliable. Or you can just in general, make the thing less reliable by kind of not caring.
Voice-matched