2 ms·
Well, that's fine but with any decision comes downsides. If you marry your critical business operations to inflexible software, or you refuse to employ even one
by chris_wot 11y ago
Well, that's fine but with any decision comes downsides. If you marry your critical business operations to inflexible software, or you refuse to employ even one developer (or maintain a contract with an external company) then you may find that down the track you cannot make important changes to your business.
Case in point: the situation detailed in this article.
My sympathy is essentially at zero level here. In this situation their privacy policy, a legal contract, guarantees they won't reveal the names of contributors even if the privacy policy changes. There is no excuse whatsoever to violate such a legal document. If they find their software cannot handle what they want to do without violating this legal contract, what this means is they cannot take the action that will violate it.
Should the MT Standard take actions to wilfully violate their privacy agreement, then they open themselves to lawsuits. In some cases I wonder if a court might grant an injunction forbidding them from implementing their new policy?