Not being PHP would have to be in my top two list for what makes good code. Not being Visual Basic would be #1.

Oh, how I wish that would happen.

nice story on this topic

One of many excellent sci-fi books by Spider Robinson.

Actually, after my follow-up email pointint out the idiocy of the reply I got, a staffer sent me a *real* email asking if I'd like to call and talk to him about it. Not that it means that they're really listening, but at least they have enough sense to not just ignore it completely. Meh.

Thanks, Representative Latta. I didn't realize that I was being an idiot. Obviously I'm just dumb.

Worse...I requested a response, which I just got. It begins:

Thank you for contacting me to voice your opposition to the recently released regulations by the Federal Communications Commission (FCC). Having recently been elected to my second term in Congress, Iâ(TM)m honored to be able to represent the people of Ohioâ(TM)s 14th Congressional District...

...which is why I emailed Rep. Latta (co-sponsor) and Rep Joyce (my rep from Ohio) and let them know that I vote, I elected one of them, and I don't support any action to reverse the FCC's recent reclassification.

I know I don't represent big bags of money, but I do directly represent a ballot. I let both of them know that I am a US Army veteran, a long-time IT professional, and a proponent of net neutrality and classifying internet service under Title II.

I don't know whether they are or aren't, but that's a tangential issue. What is it that you're concerned the government will be able to do that they don't or can't do currently if internet service is classified under Title II?

...because thinking that Title II should apply to data and not just POTS means you're short-sighted?

If you were talking about a spanned volume, I'd understand why you might be frustrated. With RAID, there's a physical relationship between the organization of the blocks of data, and the number and configuration of disks in the set.

If you have 4 disks in a stripe set, then the first 4 blocks of data go to each drive in sequence. The next 4 blocks do the same. Once you're on the billionth block, and you run out of space, you can't just add a new drive into the mix without having to rearrange all but the first 4 blocks.

For RAID levels that include mirroring, doing what you want would be technically possible.

It's certainly possible that someone could write code in the RAID firmware or software to take the mirrored drives out of the array, build a new array using them and 1 of 2 newly-added drives, copy the data from the original stripe set to the new larger one, switch to the new stripe set as the active one, add the second of the 2 newly-added drives to the old stripe set, and rebuild the updated original stripe set via mirroring, but there are more than a few potential disasters waiting to happen in that scenario.

While it might be technically possible to come up with a way to tack a disk on to a RAID 10 array, it would not be safe, and safety is one of the things that the letter R in RAID brings to the table (redundancy). If the process of adding the disks breaks redundancy (which it would have to, while it was happening), then that would be something that most folks would not be looking for as an option.

If you're saying Windows XP was a decent OS because the UI was consistent, then you will never understand why I'm saying that Windows XP was horrible. It was a kludgy, buggy, security-hole-riddled skinned refresh of Windows 2000 (most of those changes they thankfully left out of Windows Server 2003).

Windows Vista was a decent comeback with it's own personality problems, and Windows 7 fixed most of the perceived issues. Windows 8/8.1 has metro/modern silliness, but it works very well, is less crash-prone than Win7, which was less crash-prone than Win2K (no need to mention windows XP in that list), and has pretty good performance, as well.

Your points about how XP was a good OS are points I find generally unimportant to the way in which I judge operating systems, although I understand why they might be important to you.