Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
I'd be surprised, since even Google Analytics itself is affected...
Anyway, please be careful before announcing "Chrome usage surpassed this or that"
Even if the page is being prerendered, it still means Chrome is being used.
Observing ungrateful people like you.
Respect?? That's absolutely terrible.
A modern journalling filesystem should not experience any corruption after a crash, because journal recovery is supposed to keep data structures consistent.
Not only that, but NO filesystem, journalling or not, should cause a kernel crash if it is corrupted.
Microsoft has done one thing well, and that is to lower the expectations of their users so far, that what should have been a few second journal recovery turned into a big outage and manual recovery of a massively corrupted filesystem, and that gains them "Absolute respect".
Now you go tell that to Btrfs creators, son. The same people that didn't release a proper fsck yet. I've experienced major kernel panics while dealing with a corrupted Btrfs filesystem.
You may not like it, but NTFS is pretty resilient.
Ps.: I am a GNU/Linux user.
Linus is back to GNOME.
Now go back to your cave, troll.