Let me give you an analogy: If you e.g. figure out some undocumented endpoints for a REST API, which are intended for internal use only, and started using them, do you expect the developers to inform you about changes?
As far as AMD is concerned, this was never supported, nor documented. Now pulling the rug with a firmware update isn't a very nice thing to do, but maybe they've had some actual reason for that beyond "this shouldn't be enabled". Nobody should expect undocumented and unsupported features to just continue to work in perpetuity, simply because they did work at some point in the past.
This was never marketed as a feature of the consumer CPUs and if some malignant actor does get physical access to my (consumer) hardware, then them being able to read out bytes through cryo-freezing the RAM really isn't high up on the list of things I'm going to worry about.
> Amazon could effectively brick your device if so desired.
I have a 16 year old Kindle (Keyboard) that Amazon actually decided to turn into a brick last month [0]. Still works just fine and will continue to do so thanks to Calibre, but buying books from Amazon, or using their "Send to device" feature (both through the e-mail convert and for books already in my Amazon library) is now forever closed for me and de-registering the device will brick it with no recourse.
A fully reusable Starship has a launch cost of around $75m - $90m and the last V3 launch managed 44 tonnes of payload on a sub-orbital flight of not even 200km (Starlink satellites have an orbit of around 550km). That's an optimistic launch cost of $1.700/kg for a rather meaningless altitude and assuming a fully reusable Starship that doesn't keep blowing up.
I have no idea where you pulled your $400/kg number from, but it's complete and utter nonsense. To be economical at all, Starship needs to reach its target capacity of 100 tonnes to orbit, which is simply never going to happen. But even if it somehow does, it's physically impossible for Starship to ever make it further than the moon, at extreme costs, due to the refuelling requirements and fuel boil-off in orbit.
It was just another marketing stunt to pump the stock price before their terrible earnings report. One "unsupervised" unit, with the supervisor in a follow car, that nobody could actually get and drive around in.
For the last few quarters, Tesla was only profitable due to their selling CAFE credits. With those gone and their sales declining, it's all but certain that Tesla will post a loss for Q4, unless they resort to some very creative accounting tricks.
They're declining worldwide and since Musk got the climate change denier elected who did away with CAFE credits at the end of Q3, Tesla is now also no longer a profitable company.
Tesla was only profitable the last few quarters due to selling their carbon credits to other companies. They'd have lost money otherwise. And since Trump basically did away with that, Tesla is no longer a profitable company now.
As far as AMD is concerned, this was never supported, nor documented. Now pulling the rug with a firmware update isn't a very nice thing to do, but maybe they've had some actual reason for that beyond "this shouldn't be enabled". Nobody should expect undocumented and unsupported features to just continue to work in perpetuity, simply because they did work at some point in the past.