Forgot your password?
typodupeerror

Comment Re: That which is measured (Score 1) 20

Indeed. Here in California we are the poster children for this, because we have a 55 mph speed limit while towing which is NEVER enforced. We have a requirement that headlights be aimed correctly, same. We have a law saying that if there are five or more people behind you, you must pull over at the first safe opportunity to let them pass, same. Fender flares must project as far as tires, same. (Anyone who's ever had a rock break their windshield understands.)

CHP cares specifically and only about revenue generation, so they do nothing to improve safety except go after speeders. That's not nothing, but it's not enough.

Comment Re:It's simple... (Score 1) 209

It's an argument for those of us who are happy with simplicity/manual operation for less cost.

Manual windows don't reduce cost much unless you're going to put them on a lot of vehicles, otherwise it's just more parts you need to design and stock, meanwhile window motors are shared between multiple vehicles. Statistically nobody would rather have manual windows on a vehicle which costs even $40k so it might actually increase costs to offer them.

Comment Re:And are permanent? (Score 1) 88

Do you really mean that if your git repo were corrupted, restoring a snapshot of the repo from backups wouldn't work? If that's true, then it sounds like your backup system is broken. The hashes after restoring ought to be identical to what they were before the backup.

If git used the files' iNode numbers for its hashes, then I could understand how a filesystem-based backup/restore might not really work; you'd have to backup at the block level instead. But git doesn't use the iNode numbers.

git isn't magical. It only knows files. It doesn't know if you moved the repo, copied the the repo, or restored the repo from a ten year old backup. I have moved git repos around plenty of times, `cp -a`ed directories with repos, tared and un-tared directories that contain repos, and the copies have always Just Worked without any hash mismatches.

mkdir ~/test. cd ~/test. git init, touch test.txt, git add test.txt and git commit. cp -a ~/test ~/test2. cd ~/test2 and check out the backup repo. The backup is valid. Then simulate a disaster with rm -rf ~/test. Then recover from the disaster with cp -a ~/test2 ~/test and you've just restored a repo from filesystem-level backup. The resulting repo works perfectly and its hashes aren't off. git has no idea you deleted and restored under its nose. Try it yourself.

What am I missing? I'm not surprised to be called idiotic, and the shoe often fits. But I'm surprised to be called that over this.

Comment I don't ask FCC to "allow" me anything (Score 3) 59

My router's hardware's parts were made in China. Its software was made as a worldwide effort but the team seems to be officially based in the Netherlands. And I'm not asking my government's permission for updating either one. Trumptards and their micromanaging far-left centralized-economic-planners can go fuck themselves. Keep your damn dirty ape hands off my computers, comrade.

Comment Re:It's all about design (Score 1) 209

Trucks need range because - tow!

The vast majority of pickups are never used to tow anything for their entire existence, not even once. This is probably not true in the UK, but here in the US they often serve the same market that a luxury car normally would, but for people with tiny PP syndrome.

Slashdot Top Deals

When you don't know what to do, walk fast and look worried.

Working...