XPost: comp.os.linux.advocacy   
   From: hpt@invalid.invalid   
      
   Homer wrote:   
   > Lawrence D'Oliveiro spake thusly:   
   >> 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.   
      
   For an operating system that is almost a decade old now, I have yet to see   
   a WinXP Pro desktop in the workplace remain stable for more than 4 days   
   without a reboot. After an extended weekend even with a reboot   
   before going home Friday, I stare at the virtual memory error pop-up   
   window on the first day of the week. Sometimes, the system is   
   completely locked up or non-responsive, requiring pulling the plug from   
   the rear of the machine or popping out the battery from the laptop, to   
   enable reboot. You'd think that by now with all the patches, it would be   
   rock stable. You'd think pushing patches would work flawlessly.   
      
   Nada. Zip.   
      
   Then add the grind-grind-grind of the hard disk after a reboot   
   before one can start any useful work in WinXP desktop. To add insult to   
   injury, I fixed a friend's Vista laptop. That made the grind-grind-grind   
   of WinXP minor in comparison. The sucker wouldn't stop grind-grind-grind   
   for at least 8 - 10 minutes.   
      
   I like Ubuntu, latest edition. I have a useable desktop shortly after I   
   log in, no grind-grind-grind. I am immediately productive.   
      
   So much for Windows. You wonder why sysadmins and corporate exec are   
   reluctant to go to any future Windows technology after WinXP. It doesn't   
   require an advance degree to figure out.   
      
   --   
   HPT   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)