Nothing has changed.

When applying a hash+salt to a password to store in a database, you run it a bunch of times to take up an attacker's cpu time. By picking the number of repeated hashes, processing a password->hash attempt can be made to take any amount of cpu power. When designing a system, one attempts to choose a value such that, with current systems, it takes a reasonable amount of time to process a login but also too long for an attacker to brute force.

TFA talks a lot about the 'number of possible combinations', but in reality that is not strictly relevant.

What matters here is only how much more cpu power is available to attackers than to the site owner. This ratio is what determines the number of 'combinations' required to defend against attack by someone who steals the database. So, if attackers start using hardware to run hash algorithms, sites can as well, and the same balance would be maintained.

Biometric door locks? YES
Large-scale projected holograms? NO
HUD glasses for driving? NO
Weather control? NO
Dehydrated pizza? NO
Technological police state with instant conviction for crimes? WORKING ON IT

The issue with "undocumented" labor taking jobs is that minimum wage laws are selectively enforced, not that they are willing to accept a lower wage. In most cases, if a citizen attempts to get a job at an illegal rate they will be rejected, but enforcement for the most part looks the other way in the case of "undocumented" workers. If minimum wage laws were repealed, there would be plenty of citizens lining up to take these jobs at the lower rate.

Bytecode interpreters, as opposed to scripting languages, have a very real advantage that is unrelated to speed: you can use any language. If the target is the .net CLR, you can use C#, VB.NET, C++, F#...plus about a hundred others. Going with the .NET platform allows the language to be flexible, whereas with javascript you're stuck with a hacked language with no internal consistency, ridiculously stupid semantics in some cases, and a loosely typed straitjacket that causes problems in any larger application. Of course if we're using .NET and you LIKE the javascript language, a compiler could easily be developed that compiles it to .NET IL. The opposite is not true.

Nobody else has a drawer full of hacked CVS "one time use" cameras and camcorders? :D

40 years, that was.

Any chance of terrestrial contamination? Seems possible that over the last 4 years in storage, at some point the moon rocks in question could have been exposed to moisture from the Earth.

Historically in the US, the judge is the arbiter of questions of law. Questions of fact are for juries.

Worse, if you RTFA you will see discussion of the fact that moon rock samples were twice given to each of the 50 states and to each existing country at the time.

There is absolutely no reason to assume that with all those countries, all of them legally prohibited the transfer of state gifts to private individuals. I'm sure several of those could be privately held, completely legally.

Of course, it would still be super rare and the owner would likely retain the gift set itself, which would pretty easily differentiate the sample from those stolen from NASA.

Comcast is likely your only choice because the government has already interfered in the matter to make it the case. But even if it is truly so that only Comcast wishes to provide service to the area, it is still better than the government taxing you $100 a month and providing you crappy internet access whether you want it or not.

And, if the current single provider situation is not due to government interference, it is likely that sometime in the future you could get a better option. Government services tend to be slow to change and wasteful.

Sure, if you're stealing $0.10 each from 10 million different people, the people are unlikely to notice. But if you steal $0.10 ten million times from the same person they will certainly notice.

If it's a large sum from a single person I don't see how that is any different.

Theft would seem to be a problem for the Bitcoin system. Under current law, if I find something someone else has and can prove that it was stolen from me, I can force its return regardless of how the current 'owner' got it.

Since Bitcoins are by nature traceable back through every transaction, the retrieval of stolen coins can be taken to the extreme. If I somehow see a coin which was stolen from me, I could retrieve it from the current 'owner' years later. This 'owner' could have obtained the coin through a completely legit transaction, and yet now they have lost their coin through a process they could not avoid. This sort of risk is not present with cash, since after a few transactions it becomes difficult to trace back to the theft.

That is, Bitcoin transactions are actually not final because their return can be compelled by applicable law. Large-scale theft in the manner you describe would likely destroy the currency itself.

Pilots still use the bathroom, right? And if the flight is super long maybe they grab a meal from the galley?

Reinforced cockpit doors only work if the door is never opened. If it is opened and bad guys use that opportunity to attack, the door now means that the superior numbers of the passengers attempting to resist the attack are worthless. There is nothing they can do now to retake the plane or stop it from being used as the bad guys wish. In short, reinforced doors not only ignore but actually work against the effectiveness of the most proved defense against aircraft terrorism: regular passengers.

Add a separate head in the secure cockpit area and require that the secure door never be opened, ever, and we'd be talking real security. Until then it's just a feel-good measure that actually has a negative effect.

The difference is, with a corporation you can choose individually not to participate. If something is mandated by the government because 51% of the people vote for it, individuals who disagree cannot merely opt out.