I provided a link to Jon's post on E7. Why don't ask these questions/provide this feedback there? What are you trying to accomplish here? We are not the Windows team. The Windows team doesn't spend time here going through threads. They want this conversation
to happen on E7. So, make it happen there.
"The Windows team doesn't spend time here going through threads."
Why not? No, seriously. What's the point of channel9?
"Channel 9 is all about the conversation. Channel 9 should inspire Microsoft and our customers to talk in an honest and human voice."
I thought this place is a central hub to "talk" to Microsoft. If it's not, make it! There is a need for such a hub. Or is the prefered way for communication for MS really all those scattered msdn blogs?
And by the way - we both know the UAC behaviour won't be changed. The guy who discovered it never got an answer from the windows team, despite contacting Microsoft several times:
So what's the point in posting on that blog? Well, of course you could ask the question why I am posting here, since it's pointless to post here about that too. I am posting here because it seems to make some noise, (externally) much more people read this
forum than the e7 blog. I noticed some people who posted about that issue there and their comments were quickly buried by other comments and no one noticed it.
At the end of the day, it's you who is working at Microsoft, and if the Windows plattform will be in trouble, you guys will have trouble too. So, since it's in your interest, why don't you send a link to this thread to the windows 7 team, and ask them to
comment on this issue again? The chances are better if a fellow Softie asks them than some faceless commenter. I think the posters here made good points, why not counter them one by one by the windows team?
1. All the talk about UAC not a security feature/boundary/whatever EVEN THOUGH Microsoft touted the complete opposite just 6-8 months ago! There are plenty of links in this thread that prove this. How do they explain that? Either Microsoft didn't know what
UAC was when it developed and advertised it, or they knew it back then and don't know it now.