XPost: comp.os.linux.advocacy   
   From: usenet@slated.org   
      
   Verily I say unto thee, that Lawrence D'Oliveiro spake thusly:   
   > In message <0bcif6p41vjla8prttajjvr0npaiknn45d@4ax.com>, chrisv wrote:   
   >> Neither is watching an hourglass wondering what is going on.   
   >   
   > Ah, but did you know that each grain of virtual sand in the Microsoft   
   > Windows hourglass actually has its own Registry key? So for example   
   > when the {E3F66E37-33F4-4445-B35D-804455CB3936} grain falls, that   
   > indicates that the {E868BD2A-DA79-4D54-8554-F365C5E987A0} is about to   
   > {E53B95D8- AD26-4CA2-8DE3-7C58FF933A28} the   
   > {84F8213C-D969-4E06-92B4-8778327A1FDB}.  Then when the   
   > {36C6B20D-B18E-437A-9316-41451A8367C3} follows, that means your   
   > {B90848C8-A122-4858-A55B-CA708BA252ED}ing system is completely   
   > {2D44B7C2-B6FD-41FB-80B3-752D56FEAFBC}ed. And so on.   
      
   Joking aside, I can actually believe that's true.   
      
   IOW Microsoft lacks the imagination to create descriptive namespaces.   
      
   Either that, or they're trying to "protect" something by hiding it under   
   a veil of obfuscation. The million+ Windows viruses in the wild suggests   
   maybe this technique is somewhat less than useful, however.   
      
   Of course, there's so much convoluted bullshit in Windows, it's entirely   
   possible they exhausted the English dictionary by trying to name it all,   
   and therefore had to resort to using meaningless strings of HEX.   
      
   --   
   K.                           | Ancient Chinese Proverb:   
   http://slated.org            | "The road to Hell is paved with   
   Fedora 8 (Werewolf) on sky   | ignorant twits who know nothing   
   kernel 2.6.31.5, up 14:15    | about GNU/Linux."   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)