Attention: We are retiring the ASP.NET Community Blogs. Learn more >

To All MS Employees: How To Destroy Your Credibility in One Second, Guaranteed

Note: this entry has moved.

During last week I had a couple of different meetings (online and in person) with a bunch of Microsoft employees and we touched a big range of topics. One thing I’ve told them all is that if they were willing to destroy their credibility in a snap all they have to do is to try to defend the obsolete Internet Explorer or the non-working GDN Worskpaces. Any of these two positions will have the same instant effect: zero credibility for you.

7 Comments



  • Well done. It's good that someone is given a chance to tell them like it is.

  • While I agree that those are two of Microsoft's weaker offerings (I use FireFox rather than IE, for example), it's hard to bitch too loudly seeing as the cost for said products is $0.00.

  • Scott,



    I don't think that the $0.00 cost is an issue here, some facts:



    a) AFAIK, Microsoft never charged for IE. Back in the browser war days, the IE team was spitting out releases like crazy, the price tag was not an issue at that moment?. Then NN was defeated and after that the motivation to keep IE a competitive product just disappeared. The price was always $0.00 but the motivation to make a good product went from lets-make-the-best-browser-ever to we-dont-really-care-anymore.



    b) Microsoft has $0.00 products that are great and has people working on it, as the C# compiler, ;-)



    So, its a fact that Microsoft didn't care anymore about IE the moment they let it die years ago. And regarding GDN... its really hard to understand for me how in the world they're keeping that thing online, 'better-than-nothing' may be applicable with this.

  • What is the problem with the GDN Workspaces? I see a lot of use for this site from various projects from Microsoft and others. I've been using it myself as a user and seems useful to me. What is it that makes it so useless to you?



  • Well for a start, most of the time I try to access its down. When its not down its performance is really bad. Navigating through it its a big pain also. Try sourceforge instead, you should feel the difference.



    For example the Windows Installer XML (WiX) toolset released by Microsoft has been released to SourceForge and not GotDotNet.



    Other notorious projects like RssBandit (ok not from MS, but from an MS employee) has moved from GDN to SF.



    Besides PAG-sponsored ones I'm not sure really which 'large' MS projects are you talking about being hosted in GDN.

  • If you've never found GDN down then you're a *really* lucky man. You may also get a free XBox for that :-) I had a very different experience for sure.



    Re: MS hosted projects -- what I meant here is that I didn't knew of any 'major' MS projects hosted @ GDN besides EDRA which is a PAG-sponsored one.



    Sorry but I don't buy any of the two arguments about WiX being hosted @ SF:



    >>>However, at that time, none of the existing Shared Source...



    So it was a GDN missing feature at that time. It does have such a license now? If yes, why is it not moved to GDN? If not, what exactly are they waiting for?



    >>>Because WiX isn't a .Net project, per se, Microsoft decided

    >>>against releasing the WiX code ... on GDN



    This sounds like a really lame excuse. Based on this, SF should start to only allow projects targetting Unix which sounds non-sense to me. Luckily SF doesn't impose such a restriction and WiX could found a home there. I could not read the article because you linked to an AD :-( -- let me know the working URL and I'll read it.

  • Thanks for the updated link.



    @ 4:45AM I can't remember much, but I do remember that shortly after WiX was released to SF, WTL followed, lets see who is next :-) Then you've a couple of MS employees that prefer to host their pet projects in SF rather than GDN (and of course you will find others that prefer the other way around).



    Also, hosting @ GDN doesn't necessarily mean one is happy with it, If I remember correctly ScottW did considered moving .Text away from GDN more than once in the past.

Comments have been disabled for this content.