Come on now, arguing it's a good feature is different than arguing that it should be turned on by default for everyone with no documented option to turn it off.

Come on now, arguing it's a good feature is different than arguing that it should be turned on by default for everyone with no documented option to turn it off. I like this feature as an OPTION that is DOCUMENTED. But that's not how it was rolled out. The CC team + processes clearly failed here. And this is far from the first example of this kind of slopiness. I don't think it was malicious, but I do think it was quite obviously reckless/careless, and I feel like most of the comments here match that sentiment. Everyone and every team makes mistakes, but unfortunately I don't see the CC team really learning from those mistakes even though they keep happening. CC is not a stable or reliable tool, it is bleeding edge, and that's a tradeoff you make when you pick it over other harnesses.