I am not exactly a flag waving MS zealot, but I have to disagree with Hultin. I work as an applications consultant, and one area of business I deal with frequently is messaging/groupware. I'm a big fan of cross-platform, open source, and shareware/freeware products, and I feel no love for companies like MS that rely on brilliant marketing rather than brilliant design to succeed. Still, I have to say that when a client asks for serious groupware features, the only packages that can meet those needs are the big three (Exchange, Domino, GroupWise). I think Hultin's statement makes great rhetoric, and I wish it were true, but I think he needs to take another look at what is out there and what capabilities it has.
Many times I have seen implementations that would have been great open source solutions go the way of proprietary software just because of the lack of readily available groupware packages. (Coders take note.)
"More than 21,000 'postponed' bugs, an indeterminate number of which Microsoft is characterizing as 'real problems.' Others are requests for new functionality, and others reflect 'plain confusion as to how something is supposed to work.'"
and
"More than 27,000 'BugBug' comments.... According to Microsoft, they tend to represent 'unfinished work' or 'long-forgotten problems.'"
But then, for perspective, the article gives a third party opinion:
"'The fact that Microsoft found that many bugs indicates to me just how thorough their testing processes are,' said the Windows developer, who requested anonymity."
"Found?" Sounds to me like 48,000 bugs are issues that Microsoft knew about from the outset, but didn't have the resources to fix before their self imposed (and constantly slipping) release deadline. I thought the development process went something like: code--test--fix--repeat. According to the Anonymous Coward ZDNet quoted, I guess it's ok to stop at the testing part and pat ourselves on the back for all the bugs we found (that we created in the first place)?
I guess going without sleep affects your brain like Netscape affects your CPU. After a while, you start seeing lots of activity, but it isn't doing anything very useful.
Slashdot Mirror
I am not exactly a flag waving MS zealot, but I have to disagree with Hultin. I work as an applications consultant, and one area of business I deal with frequently is messaging/groupware. I'm a big fan of cross-platform, open source, and shareware/freeware products, and I feel no love for companies like MS that rely on brilliant marketing rather than brilliant design to succeed. Still, I have to say that when a client asks for serious groupware features, the only packages that can meet those needs are the big three (Exchange, Domino, GroupWise). I think Hultin's statement makes great rhetoric, and I wish it were true, but I think he needs to take another look at what is out there and what capabilities it has.
Many times I have seen implementations that would have been great open source solutions go the way of proprietary software just because of the lack of readily available groupware packages. (Coders take note.)
That's just my $.02. Flame on.
From the memo, detailing the bugs:
"More than 21,000 'postponed' bugs, an indeterminate number of which Microsoft is characterizing as 'real problems.' Others are requests for new functionality, and others reflect 'plain confusion as to how something is supposed to work.'"
and
"More than 27,000 'BugBug' comments.... According to Microsoft, they tend to represent 'unfinished work' or 'long-forgotten problems.'"
But then, for perspective, the article gives a third party opinion:
"'The fact that Microsoft found that many bugs indicates to me just how thorough their testing processes are,' said the Windows developer, who requested anonymity."
"Found?" Sounds to me like 48,000 bugs are issues that Microsoft knew about from the outset, but didn't have the resources to fix before their self imposed (and constantly slipping) release deadline. I thought the development process went something like: code--test--fix--repeat. According to the Anonymous Coward ZDNet quoted, I guess it's ok to stop at the testing part and pat ourselves on the back for all the bugs we found (that we created in the first place)?
I guess going without sleep affects your brain like Netscape affects your CPU. After a while, you start seeing lots of activity, but it isn't doing anything very useful.