Why this move from M$ now?
Allowing venting changes nothing, produces nothing.
The entire thing is nothing but PR. MS do not have their heads in the sand, they already know what needs to be addressed.
The question is what will be done, when, and why. They already know (have known for years) and as usual are not saying - probably beacause few outside of MS will like their answer.
Is it related to:
How many times you figure the prospective post to their blog has to go around their Pr dept before they allow the poster to post ...;)
I'm a little surprised at the cynicism, guys (and I'm an open-source advocate)...
Let's see the IEBlog for what it is - simply a corporate public relations channel, with all the advantages and caveats that that brings. Microsoft are obviously concerned about the PR debacle of the last few weeks over the state of IE. I don't think that the IEBlog itself will change much, but Microsoft do listen, and they are very sensitive to the importance of keeping the developer community on their side. The IEBlog is surely part of that effort to assuage the barrage of developer criticism and an attempt to downplay the abandonment of IE over the last couple of years.
It's a very small step, but a step forward nevertheless.
So why do MS keep parts of the API secret if not to give their own developers an advantage.
|Microsoft do listen, and they are very sensitive to the importance of keeping the developer community on their side. |
Blog? What blog:
|.Text - Application Error! |
SQL Server does not exist or access denied.
Folks - please leave the flames and rants for another time/place.
|My name is John, and I work on the Internet Explorer team. |
I read that and the first thing that crossed my mind was, "Is this some 12-step program I've stumbled upon?!"
Expect to see me at the next IE Anonymous meeting... "Hi, my name is balam, and I still use Internet Explorer..."
Brett the site is working now. You might have caught it at a bad time.
(that's why I love dynamically generated static pages, rarely fails!)
Check out this post, if they do all that IE might survive: