Physical hardware products shouldn't lose features after launch. If this was a "mistaken" feature which they suggested it was they should have disabled it on future chips.
"consumers don’t shop based on the endurance metrics even if they should"
Its been well over a decade now and neither I nor anyone I know has ever had an SSD endurance issue. So it seems like the type of problem where you should just go enterprise if you have it.
They hadn't bothered to add ipv6 support to most of their services and the ones that did have it usually were only dual stack - still requiring an ipv4 address.
Wickard V Filburn is simply bad law... The federal government has way too much power and MUCH more than was ever intended. Its not a feature it is indeed a bug. One caused by the Supreme Court.
Excel needed the x87 as well as they cared about maintaining the 80-bit precision in some places to get exactly the same recalc results. So they would have fixed it eventually most likely.
Ah but see the most important piece of information is not what the manufacturer specifies. Most mechanic friends would tell you manufacturers are over-extending the interval to make their cars look good to purchasers and because they only care about getting to the warranty end not total life of the car. While 3k miles old wisdom is out dated, if you do your own oil changes you can see a massive change in what comes out after 5k miles.
By over specifying the question you will miss out on the more important context.
The most likely culprit was talking to other nodes via their public IP instead of their local ones. That gets billed as interent traffic (most expensive). The second culprit is your database or other nodes are in different AZs and you get a x-zone bandwidth charge.
I wrote Sum Buddy using a variety of AIs. Its a full featured AI spreadsheet. It started in Gemini's web interface and moved over to claude (which was a huge increase in capability). It has a bunch of paying customers now.
I was a bit surprised by this take, because I never questioned you would get the luggage back if it survived. Having looked into it more I was pleasantly surprised that even in cases where the airplane was severely damaged luggage was returned.
If you remember the "Miracle on the Hudson", they actually carefully dried everything and couriered it back to the owners. Far beyond what I would expect.
It was different where you were but the billG and early Ballmer years devs had a lot of power. Like to the point where PMs had training on "soft power" or more bluntly how to get a dev who doesn't want to do your feature to implement how you designed. A good dev certainly wasn't going to get into any trouble refusing a "brain dead" feature in those years.
AWS is degrading on all fronts. If your a large scale business you almost certainly hit stock-outs during peak periods - the elasticity is a lie. If you are a mid scale its high prices and complexity, and finally if your just a beginner good friggin luck getting anything done now that they gutted free support and put near useless quotas on anything usable for modern AI development.