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."
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
it's a trick... get an axe!
Listen. The only people we hate more than the Romans are the fucking Judean People's Front.
P.F.J.: Yeah...
JUDITH: Splitters.
P.F.J.: Splitters...
FRANCIS: And the Judean Popular People's Front.
P.F.J.: Yeah. Oh, yeah. Splitters. Splitters...
LORETTA: And the People's Front of Judea.
P.F.J.: Yeah. Splitters. Splitters...
REG: What?
LORETTA: The People's Front of Judea. Splitters.
REG: We're the People's Front of Judea!
LORETTA: Oh. I thought we were the Popular Front.
REG: People's Front! C-huh.
FRANCIS: Whatever happened to the Popular Front, Reg?
REG: He's over there.
P.F.J.: Splitter!
"None are more hopelessly enslaved than those who falsely believe they are free." -- Goethe
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
True cooperation for the purpose of interoperability would be a very welcome change. The only question I have is: "Why is the hair on the back of my neck standing up?"
The race isn't always to the swift... but that's the way to bet!
"Embrace and extend" mean anything to you?
No one ever had to evacuate a city because the solar panels broke!
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.
Jboss stories on slashdot with no indication of what jboss is for (or why anyone would care). Didn't we go through this last year (and figure out that they were all slashvertizements?)?
Are they trying to prove that 2 wrongs make a right?
Simpy
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.
Bill Gate's saying is:
"If you can't beat 'em, have Steve Balmer fling a chair at them.
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
Parent is right, but I think it's bigger than just IBM.
I think what this suggests is that Microsoft is positioning itself to be the one that gets all the money that is supposed to be generated from OSS.
I believe Microsoft will be able to say to their wealthiest customers, "buy our product, then use this free product and we'll support both!" Effectively leaving the market "crumbs" to the small guys while capturing the wealthiest dollars.
If this experiment fails, I think they will litigate away their Linux competitors. Not like SCO claims, but more ordinary IP claims that don't really threaten IBM but drain what little resources distros have.
http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
Instead of wrapping all that foil around the basement, you should have asked the contractor for one tin ceiling in the first place.
It'd work much better against the CIA's powerful intelligence-gathering methoh49hrv90gtv2gvNO CARRIER
You can hold down the "B" button for continuous firing.
You cooperate - they prosper. Survive the M$ legal death march? Time to the write M$ jungle code. You wouldn't survive it, but will survive longer depending on how you behave. Embrace, extend and extinguish. http://en.wikipedia.org/wiki/Embrace,_extend_and_e xtinguish
Domestic spying is now "Benign Information Gathering"
THEN they laugh at you, then they fight you, then you win.
Please, for the good of Humanity, vote Obama.
my name's microsoft, but in here dey all calls me win-blows. don't worry, i'm gonna look out for ya. here, take dis left-over turkey sammwich i cribbed from da mess hall. it's yours. i want ya ta have it. no strings.
no, really, dat's a cryin shame dey stuck youse in here wid a buncha cash-addicted boneheads like us. cryin shame. but i'm gonna watch your back for ya kid. i'm gonna make it my personal business dat you get outta here in one piece.
look, i got some extra socks from da laundry. clean socks. outta my own pocket. you're gonna be all right, kid, don't worry about it.
an' i got somethin else for ya. i got it taped up under my arm here. you're gonna like dis, kid. ya ever seen one a dese before? it's a SHIV, you goddamn brat! dat's right, now take off yer goddamn pants an' put dis butter on your ass.
shaddap kid, quit yer goddamn cryin. whattaya think, you come in here an' eat a man's sammwich an' take a man's socks fer nothin'? shaddap, i said! you should feel lucky. you see oracle over dere? he don't use no butter! shoulda seen what he did to peoplesoft.
man i hate dese goddamn punks. stupid, goddamn, punks.
pr0n - keeping monitor glass spotless since 1981.
I've been working on a project with web services running in JBoss and clients connecting in .NET for over a year now (JBoss 4.x, .NET 2.0 Beta). These web services involve objects that are fairly complex. The biggest "incompatibility" we've experienced has been upgrading JBoss versions, which unfortunately introduce pervasive changes to the application.
.NET? If it exists, I sure haven't seen it. We even recently upgraded to jdk 1.5 and were able to get the services to use enum's on both ends in one day. I don't think there is any other common ground besides web services that JBoss and .NET (which I like to refer to as "not yet") could or should be compatible.
So my question is, where's the incompatibility with respect to JBoss and
And yet they have double digit growth every quarter... Maybe what you feel is different from what is actually happening.
Absolutely nothing. That is not what the lawsuit was about. All the com.ms.* stuff that Microsoft produced was appropriate - and very welcome for those wanting to write Windows specific apps.
The lawsuit was about adding proprietary extensions to the core libraries - the java.* libraries. That was specifically forbidden in the contract. Microsoft's excuse in court was that the contract didn't mention future versions.
The problem with extensions to core libraries was that the unwary would be fooled into writing non-portable programs that only run on Windows. It is obvious (or should be to the clueful) when importing com.ms.* that your program will only run on Windows. Having the compiler accept bogus java.lang.* features was a not so subtle attempt by Microsoft to trick people into writing non-portable programs without knowing it. The 100% pure Java program was an attempt to undo the damage by providing a program that checks all imported classes, methods, and fields, to check for the use of non-portable extensions.