Well, all phones intentionally slow themselves down (throttle) when they get too hot; peak CPU performance can only be maintained for a certain amount of time until it cools back down. I don't think any mobile OS directly exposes this to the user. Lowering peak performance in the long term is different, but I suspect they didn't see it as all that different.

I think the difference is that the user will notice their phone is hot and running slow, so there's some sort of feedback available.

I agree. To me, this is indicative of a deeper cultural problem. It sometimes happens if engineers don't speak up and get involved with the product. This causes a culture of engineers turning into executers, where they just execute the feature or the bugfix, without even _trying_ to think of the end user, or possible repercussions.

Not that the engineers are the ones at fault, it just seems that a culture change is needed to get everyone to care more about the customer.

> a culture change is needed to get everyone to care more about the customer

I think they care a great deal, but arrogance (as so often) leads them to lack judgement. Their ‘care’ has become a patrician “we know what’s best” (cf. not permitting MacBook Pro customers to have real keyboards because wanky Ikeabot Jony Ive finds them messy).

At some level of the company, but we don't know that the _engineers_ didn't respond like that. If you query it and get a response like "The UI team is taking care of that", there's not a whole lot you can do.