Slashdot Mirror
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."
The appropriate response is to look for the knife in the other hand.
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
Products from the two companies are similar in purpose, but very different in design. The JBoss application server, based on Java, runs on Windows, Linux and Unix systems. Microsoft's Windows-based application server tools, based on the company's .Net programming model, are part of its Windows Server operating system.
Oh, well that explains everything. One product runs everywhere, the other runs only on Windows. See? They're different!
Don't worry, though. Microsoft is working hard to correct the problem. Once they "make sure that JBoss runs well on Windows", both products will be very similar. After all, who needs Linux and Unix support?
Javascript + Nintendo DSi = DSiCade
That is all about positioning of windows servers. That is all. It says nothing about their embrace of open source. The market wants to run some Jboss. MS wants to sell some server licenses. While they do this to help themselves, they can still slam java, open source, and move people from java to .net all while they position server 2003 as a worthy jboss host.
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
"Embrace, extend, and extinguish" mean anything to you?
It's either that or
1. Attack
2. Embrace
3. Extend
Remember, this is a corporation, not a person.
You are checking your backups, aren't you?
THEN they laugh at you, then they fight you, then you win.
Please, for the good of Humanity, vote Obama.