I assume you're talking about software RAID since you're building RAIDs from cheap IDE drives. Software RAID is a cheap and easy way to protect your data, but if you're looking for availability, pricier SCSI RAID cards and such are the only way to go.
I use Linux Software RAID on my web server, and had a hard drive crash just last week. All the data was protected on the good drive; however, when the IDE drive failed, the entire system crashed with it. And since the BIOS was set to boot from the bad disk, simply rebooting it didn't fix the problem. I had to manually go into the BIOS to get it to boot from the good disk.
I still plan to use IDE RAID, because it's a great way to cheaply back up my data. However, if you're looking for uptime and reliability, stay away from cheap IDE drives.
I don't mean to totally attack your argument. I agree that terabyte drives would be a great thing, and I hope to seem them in a couple years. However, your examples are pretty flawed.
If in the future we switch to uncompressed data (which would be a good thing) we are definately going to need TB drives.
In nearly all cases, data compression is a good thing. Over the past few years, data compression has only gotten better, with MPEG, MP3, and OGG formats. Unless you're producing video, there's no reason to go with uncompressed formats.
And what if the industry decides to move to 60fps instead of the traditional 24fps for film and 30fps for TV? Double the frames, double the data.
The human eye can only see around 10-15 images a second. There's really no reason to go with a higher frame rate than what is currently used. I believe the reason TVs use 30fps (NTSC) and 25fps (PAL) is simply an easy rate to generate given the 60Hz/50Hz alternating current that's standard in most countries. There's really no reason anyone would ever want to use a higher frame rate.
Obligatory Natalie Portman Comment
on
Star Wars Origami
·
· Score: 3, Funny
Star Wars Origami features about a dozen pieces of Star Wars vehicles and characters
What a disappointment... the article gets slashdotted, yet they left out the only character who helped salvage the past two episodes...
I was shocked that the New York Times Mangzine article about this film neglected to mention any of the copyright issues. Very few (no?) motion pictures have yet entered the public domain.
Prior to 1978, copyrights didn't last nearly as long as they do now. Without renewals, copyright protection only lasted 28 years. Surely, there's plenty of films in the public domain from the 1910's and 1920's.
If Back truly went back to the previous page viewed, instead of using a tree, as it currently does, wouldn't this just put you in an infinite loop between two pages?
I view page #1, then page #2, then page #3. I click Back, which brings me from page #3 to page #2. Now, if I click Back again, wouldn't it just bring be back to page #3.
Obviously, they've come up with a better algorithm than simply displaying the previous page viewed, but it sure seems counterintuitive to me.
I assume you're talking about software RAID since you're building RAIDs from cheap IDE drives. Software RAID is a cheap and easy way to protect your data, but if you're looking for availability, pricier SCSI RAID cards and such are the only way to go.
I use Linux Software RAID on my web server, and had a hard drive crash just last week. All the data was protected on the good drive; however, when the IDE drive failed, the entire system crashed with it. And since the BIOS was set to boot from the bad disk, simply rebooting it didn't fix the problem. I had to manually go into the BIOS to get it to boot from the good disk.
I still plan to use IDE RAID, because it's a great way to cheaply back up my data. However, if you're looking for uptime and reliability, stay away from cheap IDE drives.
I don't mean to totally attack your argument. I agree that terabyte drives would be a great thing, and I hope to seem them in a couple years. However, your examples are pretty flawed.
If in the future we switch to uncompressed data (which would be a good thing) we are definately going to need TB drives.
In nearly all cases, data compression is a good thing. Over the past few years, data compression has only gotten better, with MPEG, MP3, and OGG formats. Unless you're producing video, there's no reason to go with uncompressed formats.
And what if the industry decides to move to 60fps instead of the traditional 24fps for film and 30fps for TV? Double the frames, double the data.
The human eye can only see around 10-15 images a second. There's really no reason to go with a higher frame rate than what is currently used. I believe the reason TVs use 30fps (NTSC) and 25fps (PAL) is simply an easy rate to generate given the 60Hz/50Hz alternating current that's standard in most countries. There's really no reason anyone would ever want to use a higher frame rate.
Star Wars Origami features about a dozen pieces of Star Wars vehicles and characters ... the article gets slashdotted, yet they left out the only character who helped salvage the past two episodes...
What a disappointment
I was shocked that the New York Times Mangzine article about this film neglected to mention any of the copyright issues. Very few (no?) motion pictures have yet entered the public domain.
Prior to 1978, copyrights didn't last nearly as long as they do now. Without renewals, copyright protection only lasted 28 years. Surely, there's plenty of films in the public domain from the 1910's and 1920's.
I doubt the hard drive's going to have an error on every single write operation, so maybe 99.998% detection is enough.
Does anyone know how this compares to typical IDE drives?
Pros: ...
Very Quiet
Sending serially, one bit at a time, is quieter than in parallel? I didn't know bits made so much noise
If Back truly went back to the previous page viewed, instead of using a tree, as it currently does, wouldn't this just put you in an infinite loop between two pages? I view page #1, then page #2, then page #3. I click Back, which brings me from page #3 to page #2. Now, if I click Back again, wouldn't it just bring be back to page #3. Obviously, they've come up with a better algorithm than simply displaying the previous page viewed, but it sure seems counterintuitive to me.