You said they would “shut it down,” which can reasonably be interpreted as killing the feature. If you meant something more specific, you should have said that. Clarity is the duty of the speaker.
>> “If everyone started using S3 for this purpose, they would shut it down pretty quickly.”
> “I never said they would kill the feature. I said they would shut down the behavior.”
Seems "it" is standing in for a lot of nuance here.
With these three sentences side by side, still took a while to see how you might be referring to the "everyone using" behavior instead of the "S3 purpose" feature! Usually given ambiguity the nearest plausible reference wins.
Since in tech "shut it down" is more often systems than humans and that was the nearest reference "it" could refer to, took some doing to see how your assertion "I said the behavior" could be accurate!
I'll concede that "it" was ambiguous. Though if you take the most literal version of what I said, it would be they'd shut down S3, which clearly isn't true.
We can continue to debate whether or not I (who worked on that team and generally understands what goes into building scaled cloud services, having built several myself) understand how a cloud provider responds to customers using your service in a way you clearly didn't intend, or we can move on with our day.
I wasn't debating what you know from the vantage of someone who's founded and built global cloud SaaS services at scale for a while. I was noting how it was ambiguous but going further to say "ah, I see how you can assert you said it," giving you credit.
