This doesn't matter; it's post-sale enshittification... They didn't even wait to make the next model shittier!

Also, it probably wasn't the selling point, but it was the baseline of quality, and probably documented online or in manuals.

Furthermore, accepting this as normal opens the door to further post-sale enshittification of ALL things. Next thing you know, upgrades here and there are going to degrade the quality of products and services just because it wasn't explicitly written (think post-upgrade slowdowns of mobile phones to pressure people to buy newer ones).

This is THE slipperiest slope; and it's just taking place because the deregulation mafia is turning a blind eye to these tech cartels.

▲

ChocolateGod 7 hours ago | parent [-]

This is FUD. We have no idea the reason why.

Given it was never marketed, it's possible perhaps despite the feature being exposed it never worked correctly and AMD saw fit to just disable it rather than people get a false sense of security through it.

▲

red-iron-pine 5 hours ago | parent | next [-]

the fact they won't tell us why is the concern.

"no one uses it and there is a bug" may invite more questions or panic, but "that's all we're going to say" implies that Mythos found something scary, or that the NSA demanded they all get turned off.

▲

63stack 2 hours ago | parent | prev | next [-]

AMD is spreading FUD by not answering why it was removed. They could stop this in its tracks if they wanted.

▲

pluralmonad 6 hours ago | parent | prev [-]

Why call out FUD when you only have more/different uncertainty to offer?

	▲	ChocolateGod 5 hours ago \| parent [-]
		Spreading misinformation is different to suggesting possible reasons.