So am I biased on this blog?
In short (what *else* would you expect from 1/2 of Team-TSG?), yes...
I had a response on my blog entry about Microsoft and the state of Mass. deciding to ditch Office and support the OpenDocument format. Dave from Colorado (no, I looked up the IP and it wasn't from Redmond) responds:
Explain to me how this is different than us waiting for the next version of Domino to get our DB2 support? Or pick your favorite new R7 feature, and explain the difference. It seems unfair to attack MS just because they tell people that new features are coming, especially when the content you are critiquing is just a blog post of from one guy working on the team -- it isn't even an official microsoft statement.
Or let's look at this another way --
Now suppose that MS tells everyone to wait, then on the day of their product release, says, "Sorry, that feature wasn't tested enough -- wait for the next version."
If MS did that, you would be all over them. But IBM does exactly that, as an official statement no less, and nobody says a peep?
I'm not saying that any of the above is good or bad. Just pointing out that there is a major double standard going on.
Now, I think the issue I raised and the one he's taking exception to is the following snippet I highlighted in that post:
if only Massachusetts had waited to see the beta of the new version coming out in a few months
I do understand what he's trying to point out, but I *do* think there's a difference...
For one, I don't think IBM has been trying to freeze the market in collaboration by promising grandiose new functionality in ND7 that would be a vast improvement on ND6.5. To take the DB2/Domino feature, it has always been a feature that was *optional*, and that could be used in particular situations to create new and different types of applications. At no time (the way I see it) was there a push to have everyone hold off on doing anything with their Notes environment so that they could upgrade to ND7 and convert everything to DB2. Regardless of what a certain software corporation might have you believe...
Second, IBM didn't pull the feature. You can get a key to unlock it, but it's not fully supported at this time. That may be nitpicking, but I think it's a major difference. If you were waiting to build a specific application based on that feature, you can still move ahead, but carefully. Again, this has been another option that IBM has added to a wide range of choices in Notes. It's not a conversion path required to continue to use the product.
Finally, you're right in that the statement I quoted is a blog and not an official Microsoft release. Regardless, it shows the mindset of people running the show, and it gives a window into the thought processes that often play out in public. And in this case, I think the statement matches past (and future?) actions.
IBM's not perfect... It would have been nice to see an earlier statement on the DB2 deployment situation instead of hearing about it via "rumors" and such. It might have made planning for some sites easier. And the recent disappearance/reappearance of the ND7 software on the IBM sites was rather bizarre and could have been explained better instead of causing confusion and doubt for four or five days until we got a better explanation. I didn't comment on these as others in the blog circles I run in did so, and probably did so better than I might have. Still, I see these as aberrations from IBM, not a consistent track record.
Every blog out there... every *media* source out there... they all have a set of assumptions and perspectives that color their writing and reporting. My perspective is that I'm an IT professional who's good at what I do, and who makes my living with IBM software. I also feel that Microsoft is competing in the marketplace using tactics that are ethically suspect at times, and have been ruled as outright illegal at others. Therefore, I will be more forgiving of IBM than I will of Microsoft. If you read this blog, that's what you get.
(Standard disclaimers apply... My opinions, not my employers, your mileage may vary, results not typical, close cover before striking...)