Microsoft And JBoss Collaborate On Server Software
wellington map wrote to mention a C|Net article discussing a collaboration between Microsoft and JBoss, intended to ensure their server software is more interoperable. From the article: "Microsoft has struggled to deal with the arrival of open-source software, which is collaboratively developed with a code-sharing process that stands in stark contrast to the secrecy that shrouds most of the products from Microsoft and other proprietary software makers. After several attacks on the intellectual-property foundations and the methods, quality and cost of open-source software, Redmond, Wash.-based Microsoft has begun a more cooperative phase."
What is the appropriate response when you are offered a hand that started out with a knife in it?
Idiot.
I'm sure Microsoft has some plan for assimilation (this is not meant to be a troll or a flame). Hopefully this doesn't turn out like J# where Microsoft put in their own proprietary libraries that developers built on thinking they were building Java applications that could run on any JVM.
Bradley Holt
I think this has got nothing to do with FOSS but everything to do with IBM. Hitting on Websphere will be hitting on IBM's one of the server product. If you look at Microsoft website, it always compares .Net with Websphere. By collaborating with open source product MS will kill two birds in one stone. MS open source supporter and other kill websphere as much as possible by promoting an open source product.
1) Denial
2) Anger
3) Bargaining — Microsoft, you are HERE.
4) Depression
5) Acceptance
Hey, at least they're working the program. Who would have imagined 2 years ago that they would even acknowledge open source, let alone cooperate. The next 2 steps will be rough for them.
MS: Let's work with JBos to interoperate more cleanly. Once we're done, we can always change the way ours works ... I mean improve on our protocols. Our customers can now use Windows and .NET to talk to JBoss, while JBoss users can't talk to our stuff. It's brilliant, as it makes JBoss look bad. Further, it will slow down the JBoss developers who will have to spend more time playing catch-up, while setting them up so that even if they change their own protocols in a game of tit-for-tat, we can point to them and say, "look, the JBoss developers deliberately broke compatibility with our software -- aren't they evil!".
"Keep your friends close, and your enemies closer."
Sun Tzu (probably maybe)
I have plenty of common sense, I just choose to ignore it. -- Calvin