It's not a perception, it's a reality, and yes, the workers have zero power.

Ha ha ha. Nope. This is so only on paper, and only people who don't know first hand how it works will be fooled by that (meaning: most politicians and public).

Only if there is a labor department certification for the other position, can someone on H-1B apply for it. So, it's not possible to change jobs, unless the other job is already set up to accept an H-1B worker. This almost never happens, because if you're setting up for an H-1B, you have a particular applicant in mind anyway - otherwise there's really no point to H-1B, from an employer perspective. H-1B costs time and money, and if you don't have a vetted person lined up, it's a pointless exercise.

> the police could be sued if they wasted any time at all.

Sure, and the suit would be dropped upon filing. Just because you can sue anyone doesn't mean the case got any legs to stand on. At least in the U.S., none of the public emergency services have any duty to do anything at all.

The obvious response: the easter eggs need to be made a part of the requirements.

Think of it like this: would you think highly of a physics/engineering book that showed free body diagrams with mistakes in them? This is the same kind of a thing. It's a hack job that could have be made into something great, but wasn't.

I must be weird then. I tried to kill myself once, and I put extra care into making sure that I didn't make anyone suffer unnecessarily. Sure I had family and whatnot, their suffering couldn't be helped, but I chose a way to go that would not expose any additional people to suffering, and certainly I couldn't even imagine physically hurting anyone while doing so - it'd be a truly despicable act. The way I went about it, it'd be very unlikely that anyone would accidentally find my body or witness my death.

Frankly said, H&H was, at least in the editions I had access to, full of circuits that either outright didn't work, or barely worked, and seemed like a slightly overpraised hack. I don't recommend that book to anyone.

You can tune the piano for any temperament you wish.

Motors at the wheels actually don't make much engineering sense. They only look sensible if you haven't run the numbers and haven't done real design work. Most electric cars out there are not gas platforms, and would make very poor gas platforms. So you kinda made your problems up.

When you connect/disconnect them, the high current circuit is off. There's only a limited-current control circuit available, and I'm not sure if that circuit isn't designed for inherent safety in explosive environments. It certainly could be.

So, Microsoft is still Microsoft. Good to know.

Firmware is stored on the magnetic medium on hard drives, so I don't see why they'd do it any other way on SSDs. Over the hundreds of millions of drives shipped, not having a large dedicated firmware flash saves real money.

It'd be a rather different design today. These parts simply had a process issue, they'd have failed whether they were ROMs or something else.

I presume that the drive treats its firmware as just a special range of blocks/sectors, subject to the same management as everything else. Eventually, you power cycle it, and the bootloader can't find any viable firmware blocks. It then appears bricked. That's the only explanation I see.

There are no limited lifespan devices on an RPI, of any revision, other than flash memory. If you replaced the boot flash and SD flash with mask-programmed devices, it'd certainly boot a 100 years from now. No doubt about it.