by patentedlicks » Mon Mar 18, 2013 8:19 pm
Is there some reason that MediaMonkey announces its many bugs when there is nothing to do but click the warning alert away, and let the program keep on its faulty way? The only reason I can think to be so obnoxious is to remind MediaMonkey users how bad the programmers are who work on MediaMonkey. Otherwise they would have an exception (error) handling system that caught these errors as they rose on the stack and snuff them before their announcement. Final product, after all, isn't supposed to be run in debug mode. But maybe the Mediamonkey programmers don't know that either; as if they work in a state of arrested beta.
Is there some reason that MediaMonkey announces its many bugs when there is nothing to do but click the warning alert away, and let the program keep on its faulty way? The only reason I can think to be so obnoxious is to remind MediaMonkey users how bad the programmers are who work on MediaMonkey. Otherwise they would have an exception (error) handling system that caught these errors as they rose on the stack and snuff them before their announcement. Final product, after all, isn't supposed to be run in debug mode. But maybe the Mediamonkey programmers don't know that either; as if they work in a state of arrested beta.
