No, because people coded to the API they were given. They got permission through the application's manifest, as specified by the documentation. They coded to standards. Dynamically revoking permissions breaks that contract.
It sounds like you are more familiar with web frontend programming. I'd caution you that Android app development has differences that are important to this discussion.
>> "Dynamically revoking permissions breaks that contract."
While I'm no expert in native app dev, it's interesting to see so many people are so confident the apps will break under those circumstances, without actually any first hand experience.
I would likewise caution anyone putting forward this idea, that unless you've seen the effect revoking permissions has had on your app, or another app, then anything you put forward in this discussion is hearsay.
I'm not jumping on the meme train about millions of apps crashing due to permission revoking. Google should just include the feature, and have it default to off, with appropriate warnings about tripping some apps when switched on. It doesn't need to be a complicated thing.
It sounds like you are more familiar with web frontend programming. I'd caution you that Android app development has differences that are important to this discussion.