Really? I wish they would invest some of that fastidiousness in choosing better disk drives. The drive on my ThinkPad T500 crapped out after a mere six months. This after I paid for what I thought was top-of-the-line hardware.
I was backed up, but it took me several days to reload all the software and get running again. Very unpleasant experience.
Now I can't get Acronis True Image to mirror my whole drive. The last time I tried, my system seized up, I had to lean on the power button for ten seconds to shut it down, and when I rebooted I got a nice message saying "Your system may not restart". Wonderful.
Oh - and the fingerprint scanner stops working after three months. The twerp in tech support casually suggested I would have to "reflash my BIOS". Really? I see you don't user your PC to earn a living.
I never had such grief with generic black boxes.
The most common use of "goto" in that circumstance is to enforce "only one return".
Which is every bit the pedantic lunacy that goto-hate is.
Not necessarily: sometimes you need to free memory, resources, etc.
I don't use goto anymore, but back in the days of 16-bit and 12K stack, where we had to malloc() local variables, a 'one return' goto proved useful to branch to free() without excessively nested 'if's.
The volunteer fire brigade is no longer necessary?
Not so. In rural communities, the tax burden of a paid fire department would be unaffordable. The volunteer fire brigade is a vital and respected part of the community.
We ran the update once a day on the 40,000-card master file, using the 1,000 card/minute reader. There were a couple of jams each day. Once a wad of cards got caught in the pinch rollers: smoke started billowing out of the car reader. Good times.
Real programs don't eat cache.