8 ms·

That helps, but can someone provide a babblefish translation of what this means for those of us who don't live in the Java world? Is it basically... Dear Java,

That helps, but can someone provide a babblefish translation of what this means for those of us who don't live in the Java world? Is it basically... Dear Java, We remember when you used to be cool. Now you spend all of your time drinking and hanging out with lawyers. We are leaving and taking the dog and all of the CDs with us. Love, Apache

lenni 16y ago
I believe that is basically it. They won't be participating in writing specifications, but I don't think that anyone will be stopping Apache (or anyone else) from implementing any of the JSRs. If a hypothetical Java Servlet API v4.0 would be released they could still make Tomcat be compliant with it. On the other hand Tomcat is very widely used in the not-quite-huge-enterprise companies and it is obviously helpful for a spec if all implementers can agree on some common ground before it is written. ECMA probably wouldn't see a point in doing ES5 if Microsoft and Mozilla would not talk to them.
- yesno 16y ago
  It might be a matter of time before Oracle decided to cut all of the oxygen lines for these open source solutions judging from Ellison's comment about RedHat business models. What do you think would happen in order for a library to be certified (passed a certain TCK) would require to pay Oracle a huge amount of money? Oracle can get more money from IBM, RedHat, SpringSource (SS uses a modified Tomcat for their tcServer) and a slew bunch of other companies. Whether they'll do it or not, I don't know.
kbutler 16y ago
Dear Java, You said you wanted to be friends, but Oracle just wants us as fans. We need more in a relationship. Love, Apache
maddalab 16y ago
Translation : We are breaking up, except this time, it's not me, it's you -Kicking ass and taking names