Are you saying that a FC SAN will give you fewer IOps than this DIMM SSD?
He's talking about latency, not throughput.

So... Everyone should be unhappy so that individuals should be happy?

That's a lot higher than your piece of pie
In fact, that's a lot lower.
1mL is about 1g (true for water, nearly true for alcohol)
So, to have about 4mL of alcohol, you'd need about 10L of orange juice.
BTW, here's your corrected link:
http://www.sweetpoison.com/articles/dr-woodrow-monte10.html

I suggest you read up on cryptography.
Encryption, in general, is attempting exactly what you're attempting: make plaintext look random.
What you're trying to defend against is known as a "known-plaintext attack".
You can use any standard cryptographic approach such as AES-CBC as suggested above.
For a password-based approach, there are also standard key generation algorithms such as PKCS #5.
Note that your claim that your approach gives "as random as it gets" data is not true; once you've fixed for all time a set of random numbers, they're no longer "random".
As for generating random-like numbers deterministically, that's what stream ciphers (e.g. RC4) do.

This is about as believable as the post about DuPont.
Hemp is still being cultivated commercially. It hasn't revolutionized anything.

non-UTF8 in filenames
UTF8 can represent all of Unicode.
I'm not aware of any non-unicode characters.

Turing B into He seems like fission, not fusion. Is that what a fusor does?
Also, you seem to write that the reaction generates energy. If that's the case, you don't "need" gigawatts, you produce them (from that particular reaction anyway)

Well, POSIX requires CHAR_BIT to be 8, so if you change that it's normal if it breaks.
But otherwise to test portability this seems interesting, although it would be most interesting if it could detect when something isn't done right.
Most importantly though, you'd need a compiler to target this architecture.
For instance, NULL being 0 is usually not part of the computer architecture itself; 0 is addressable on x86, causing this bug:
http://lwn.net/Articles/341773/

So a 1.3% difference in radius is "trivially easy to miss" but 4% is "one hell of an oversight"?
(1.04^(1/3) is about 1.013)

This led me to look at the wikipedia article for "radiometer".
A radiometer measures the strength of the radiation; whether the measurable effect is caused by heat or anything else is not relevant as long as it's proportional to the quantity being measured; in that sense the common toy *is* a radiometer.
As for the reason it moves, it turns out it's more complicated than that.

What would be the crime?
Obstruction of justice?

Let's see...
128 bits = 2^128 possibilities
2^128 > (2^10)^12 = 1024^12 > 10^36
Supercomputer we're talking about = 10^18 operations/s
Meaning it would take about 10^18s (about the age of the universe) to cycle through 128bit keyspace.

encrypting a DVD in no way prevents you from making copies of it (copies of encrypted bits play just like the original)
Typically you can't burn the "key" part of a DVD, so a player can't decrypt the encrypted bits on the copy.

While I haven't used C#, from what I've heard it's vastly superior to Java; so I understand if you like it.
However, still from what I've heard, mono is a very poor implementation of .Net. For instance, the VM uses a GC designed for C, and apparently the library is not written especially carefully.

It's not a bug, it's a feature.