Linked by David Adams on Mon 7th Jul 2008 17:55 UTC
A Silicon.com article takes a look into the crystal ball, with Bill Gates departing from Microsoft, and posits the following potential changes: 1. A greater acceptance of open source 2. A new approach to Windows releases 3. Secure new revenue by buying big 4. Taking the web seriously through interoperability 5. More Microsoft than Gates [letting new people make decisions].
Thread beginning with comment 321794
To read all comments associated with this story, please click here.
Big problem here is that MS refuses to ship open source, even when it makes sense. I don't know as much about the windows world, but in the dev world it is all over.
Entity Framework was a big resounding failure, people wanted NHibernate with better integration and tooling, not LINQ2SQL with a better design surface.
TFS source control is confusing, as after all these years of effort they have almost got something almost on par with SVN. Why didn't they just buy tortoise?
MSTest, oh how I hate thee. Roughly the same as NUnit, just wayyyyyyyyyy slower. Why? NIH. There was no reason for MSTest, and after its second revision it is still hands down the worst testing framework in .net.
MSBuild. Why?? Same deal as MSTest, a gigantic reinvention of the relatively mature NAnt.
Unity Framework. Ok, lets see, we have StructureMap which is very mature and feature rich, CastleWindsor which has been around for ages, Spring.Net which has roots in a project that has been around since BEFORE .net existed, and Ninject, which is a kickass innovative lightweight container. Why in the name of god do we need another half baked, over engineered IoC container?
I could go on. MS has some fantastic tools, but there are plenty of places that they don't have anything, and open source has robust, mature frameworks.
And yes, I am bitter about this.
2. A new approach to Windows releases
One of the great new features of the new windows release management is that nobody is talking anymore about what they are doing. Sure, that bit them on the ass for Vista, but I'm sure everybody would rather they solved the problem by talking and LISTENING rather then just not talking anymore.
3. Secure new revenue by buying big
They also have to dodge the anti-trust stick, so buying big has to be done extremely carefully.
4. Taking the web seriously through interoperability
Here I agree, although for some reason they talk about ODF (of all things) and live mesh in this bullet point. What about IE8??!?
IE7 was the first sign of things getting better, but IE8 will be a major step towards regaining credibility in the web world. IE8 will not fix everything, but it will seriously raise the "least common denominator" bar that those of us who do web work have to deal with.
5. More Microsoft than Gates [letting new people make decisions].
This point was utter fluff. Gates has been out of the picture for years now, Ballmer has been the (slightly psychotic) face of MS in the media for quite awhile. Maybe not for the WIRED crowd, but definitely people who read OSNews.
I don't understand how this could be considered the least bit insightful.
Member since:
2006-02-05
Big problem here is that MS refuses to ship open source, even when it makes sense. I don't know as much about the windows world, but in the dev world it is all over.
Entity Framework was a big resounding failure, people wanted NHibernate with better integration and tooling, not LINQ2SQL with a better design surface.
TFS source control is confusing, as after all these years of effort they have almost got something almost on par with SVN. Why didn't they just buy tortoise?
MSTest, oh how I hate thee. Roughly the same as NUnit, just wayyyyyyyyyy slower. Why? NIH. There was no reason for MSTest, and after its second revision it is still hands down the worst testing framework in .net.
MSBuild. Why?? Same deal as MSTest, a gigantic reinvention of the relatively mature NAnt.
Unity Framework. Ok, lets see, we have StructureMap which is very mature and feature rich, CastleWindsor which has been around for ages, Spring.Net which has roots in a project that has been around since BEFORE .net existed, and Ninject, which is a kickass innovative lightweight container. Why in the name of god do we need another half baked, over engineered IoC container?
I could go on. MS has some fantastic tools, but there are plenty of places that they don't have anything, and open source has robust, mature frameworks.
And yes, I am bitter about this.
One of the great new features of the new windows release management is that nobody is talking anymore about what they are doing. Sure, that bit them on the ass for Vista, but I'm sure everybody would rather they solved the problem by talking and LISTENING rather then just not talking anymore.
They also have to dodge the anti-trust stick, so buying big has to be done extremely carefully.
4. Taking the web seriously through interoperability
Here I agree, although for some reason they talk about ODF (of all things) and live mesh in this bullet point. What about IE8??!?
IE7 was the first sign of things getting better, but IE8 will be a major step towards regaining credibility in the web world. IE8 will not fix everything, but it will seriously raise the "least common denominator" bar that those of us who do web work have to deal with.
5. More Microsoft than Gates [letting new people make decisions].
This point was utter fluff. Gates has been out of the picture for years now, Ballmer has been the (slightly psychotic) face of MS in the media for quite awhile. Maybe not for the WIRED crowd, but definitely people who read OSNews.
I don't understand how this could be considered the least bit insightful.