Originally posted by jdbolick
I was tolerant back when I thought this was an unknown bug, but instead I have my thread locked and get notified that this is a bug that has been known for over a week and yet wasn't fixed.
Ever thought that it might not be all that easy to identify exactly why a certain bug is occuring, let alone how to fix it? Heck, Microsoft takes way longer than a week to fix far more glaring bugs, and they certainly can throw way more manpower at it. And even if Bort might have identified the cause and managed to fix it, he would have to at least try and make sure that the fix does not open problems in other places. To cry foul because a bug was not fixed after a mere week is simply laughable.
I was tolerant back when I thought this was an unknown bug, but instead I have my thread locked and get notified that this is a bug that has been known for over a week and yet wasn't fixed.
Ever thought that it might not be all that easy to identify exactly why a certain bug is occuring, let alone how to fix it? Heck, Microsoft takes way longer than a week to fix far more glaring bugs, and they certainly can throw way more manpower at it. And even if Bort might have identified the cause and managed to fix it, he would have to at least try and make sure that the fix does not open problems in other places. To cry foul because a bug was not fixed after a mere week is simply laughable.




.
























