While in general that may make sense, in the specifics of Twitter it’s just another unnecessary bad decision in a chain of unnecessary bad decisions.
The biggest issue isn’t what they’ve done but how they did it: dismissively, without warning, justified days later with a flimsy provably false excuse.
> A public API radically slows down product iteration since each feature needs to be considered in terms of its blast radius to third party clients.
Twitter’s public API was already lacking. There are several features, like polls, third-party clients never had access to. No one would be surprised if the API remained static forever.
> killing the API to speed up product velocity isn’t an insane move if you value that more than the existing 3rd party ecosystem.
The API wasn’t completely disabled, it’s still working for smaller clients.