A professional organization NEVER turns off features -- final, beta, experimental, it doesn't matter what you call it -- without warning unless external pressur

A professional organization NEVER turns off features -- final, beta, experimental, it doesn't matter what you call it -- without warning unless external pressures force you to. What you do is determine who is using the feature and send a warning to those customers. Then after waiting a while (a few days to a few months), you can turn it off. Predictability is critical to B2B services. It is more important than price or performance. It allows customers to make an informed decision. It prevents dissatisfaction and PR disasters. I also think this should be a lesson for younger businessmen. Customers will even get angry if you cut undocumented features. Or fix bugs they relied upon. Any change that impacts customers needs to be communicated in advance. IMO, if you truly "put developers and applications first", you would have done this. I humbly suggest some soul searching.