On the one hand I would tend to agree... on the other hand, there are a lot of developers and contributers that are not native english. I've worked on projects with other devs, who would show me some code, documentation, etc... and be completel shocked(and appalled) when I pointed out what (to me) were glaring spelling/grammatical errors. Hell, I am native english, and though I try my best, I can sometimes read and re-read text a hundred times, and miss something stupid like "you're" instead "your" or "it's" instead of "its".:P
And this is why I wait before switching fs types. I waited almost 2 years after ext3 was considered stable, before I switched from ext2. I just rebuilt my machine 2 days ago, and I almost, almost went with ext4. But that little voice of caution(read, paranoid subconcious:P) told me to hold off, then someone points out this thread to me.
With that said, after reading the posts in the mailing lists, I am once again proud of the kernel developers and the hardcore linux geeks, for so quickly jumping on this problem, as well as the calm of the "victims". If a similar problem occurred in windows, hoo-boy, there would be an uprising.
Slashdot Mirror
Haha, had a genuine laugh at this. :D Was just going to make a similar reference.
On the one hand I would tend to agree... on the other hand, there are a lot of developers and contributers that are not native english. I've worked on projects with other devs, who would show me some code, documentation, etc... and be completel shocked(and appalled) when I pointed out what (to me) were glaring spelling/grammatical errors. Hell, I am native english, and though I try my best, I can sometimes read and re-read text a hundred times, and miss something stupid like "you're" instead "your" or "it's" instead of "its". :P
And this is why I wait before switching fs types. I waited almost 2 years after ext3 was considered stable, before I switched from ext2. I just rebuilt my machine 2 days ago, and I almost, almost went with ext4. But that little voice of caution(read, paranoid subconcious :P) told me to hold off, then someone points out this thread to me.
With that said, after reading the posts in the mailing lists, I am once again proud of the kernel developers and the hardcore linux geeks, for so quickly jumping on this problem, as well as the calm of the "victims". If a similar problem occurred in windows, hoo-boy, there would be an uprising.
I read right to the end of the comments, HOPING that someone would say something like this. As DeathElk said, thank you.