Readit NewsThen - like now - it seemed that they couldn't understand that what they made was not what their customers wanted.
I'll try to add comments and answer questions where I can.
- Warren
Edit: This is a fantastic write-up by the way!
- Amazon
- Meta
That said...
We do our very best. But I don't know anyone here who would say "it can never happen". Security is never an absolute. The best processes and technology will lower the likelihood and impact towards 0, but never to 0. Viewed from that angle, it's not if Amazon will be hacked, it's when and to what extent. It is my sincere hope that if we have an incident, we rise up to the moment with transparency and humility. I believe that's what most of us are looking for during and after an incident has occurred.
To our customers: Do your best, but have a plan for what you're going to do when it happens. Incidents like this one here from checkout.com can show examples of some positive actions that can be taken.
(Intel and AMD stopped at 2! Apparently more wasn't worth it for them. Presumably because the cpu was doing enough of the right thing already.)
So hyper-threading was a way to recoup some of those losses. I recall reading at the time that it was a "latency hiding technique". How effective it was I leave to others. But it became standard it seems on all x86 processors in time. Core and Core 2 didn't seem to need it (much shorter pipelines) but later Intel and AMD processors got it.
This is how it was explained to me at the time anyways. I was working at an OEM from '02-'05, and I recall when this feature came out. I pulled out my copy of "Inside the Machine" by Jon Stokes which goes deep into the P4 architecture, but strangely I can only find a single mention of hyperthreading in the book. But it goes far into the P4 architecture and why branch misses are so punishing. It's a good read.
Edit: Adding that I suspect instruction pipelines are not so long that adding additional threads would help. I suspect diminishing returns past 2.
I'd prefer not to use the dunks as I'm uncertain they only impact mosquitos, but my insect population seems healthy. I saw a stag beetle two weeks ago! There are certainly fewer spiders though.
One thing this won't help with are the chiggers which also populate my yard. But I'll happily deal with less mosquitos. I'll look forward to giving this a try.
I mean, I'm sure there's a handful of parents who value woodworking skills but do no woodworking themselves - but are there enough to support a whole product category of $250 cardboard tools?
When he's older and bigger, then using real tools will be more practical, and we can using the real thing. The risk will be more manageable then.
At this stage however, this chompsaw looks appealing. Instead of disappointing him when he wants to drive and having to diplomatically explain that he lacks the strength and coordination to use the actual tool, I can just hand him this. Give a bit of instruction, and then let him experiment. That feeling of "hey, I'm doing this myself" is exciting to him and gives him a sense of accomplishment.
Long story short, I see this as a product aimed at a younger audience who aren't old enough to take the lead (with guidance) in the workshop yet, but want the feeling of doing it themselves in a safe way. I like it.
$250 though. Ooof.
https://bsky.app/profile/vcdgf555.bsky.social/post/3lovrqupt...
Granted, I wasn't good at video games in general. And this one infuriated me, because I loved it. I could easily beat the first level, but then I crashed on carrier landing. This happened for years. I only ever saw the first level of this game.
Then one day, while staying at my elementary afterschool sitter's house, one of the kids there told me he played Top Gun as well. He could land, but wasn't very good at the rest of the game.
A plan was formed.
The next day, I brought the cartridge over, and we settled in. I'd play the level, then hand him the controller at which point he'd plant it on the deck. Rinse and Repeat. Top Gun and Top Gun: The Second Mission didn't have too many levels, (6 maybe?) and I don't think it took us too long to beat. Neither one of us had seen much of the game. But working together, we beat both in a matter of hours.
I still look back on that as one of the few NES games I finished without codes or a Game Genie, just the help of a friend. =D