JDO vs EJB
The first sign of trouble came from some turdburglar from Goldman Sachs. This freak’s main complaint was baffling, to say the least. The asshat was annoyed and troubled by the fact that he could go with JDO OR EJB. The choice seemed to upset him, and it apparently made things very expensive and costly for him, because it forced him to waste months evaluating both. It’s at times like these that one is tempted to just despair of the whole java thing. You have all these people complaining endlessly about the lack of choice and how evil monopolies are, yet this pillowbiter comes along and complains that he’s being given a choice, and that expecting him to do his homework and perhaps even fire off a neuron or two in the dusty cobwebs between his hears is and pick a technology is, apparently, far too much to ask for.
I thought that if the questions continues to be of such pitiful quality, I might as well just leave and find the usual merry band of miscreants drinking their sorrows away.
This, apparently, was a sign of things to come. The next question came from none other than JDO zealot Robin Roos. Surprisingly, nobody bothered tell Robin that standing up to ask questions designed to bait and taunt the EJB spec in an EJB BOF is simply bad manners. No matter how pleasantly couched his question is, it’s blatantly obvious that he is NOT asking in a well intentioned I’d-really-like-to-know-about-ejb-because-I’m-curious-and-mean-well sort of way. If I wanted to listen to this sort of tawdry shite I’d just start reading TSS or something. Disgusted, I left and joined the aforementioned merry band of degenerates for a night of rampant underachieving (no details here, since Matt Raible has far too many incriminating pictures).
The whole thing got me thinking, what the fuck is wrong with these JDO and EJB spec people? Is the java world so starved of controversy and excitement that they must pretend that their pathetic little misunderstanding is worthy of a full scale squabble, to be conducted in public in the truly disgraceful manner it has been?
I don’t know if anyone saw it, but some rumpranger on the JDO spec saw fit to post a news item on TSS proclaiming tripe like ‘EJB and JDO group agree to meet during JavaOne!’. What’s particularly funny is that this announcement was NOT meant to be public, and that it turned out to be rather premature. So much so in fact that clearly someone pulled some strings at TSS and got the article deleted altogether (it no longer shows up!).
Now, even pretending that this is news is pathetic and pitiful. Are you EG members so childish that something as trivial as a discussion must be broadcast as breaking news? Are you so starved for attention that you need to try and make your little spat into something of such importance and worth?
Grow up. Meet up in private, decide what on earth you want to do, and stop making such idiots of yourselves in public. If that’s too much to ask for, then just shut up. You’re ruining the image of the JCP for the rest of us, and making it look like it’s composed of nothing but a bunch of petty vindictive biased children whose methods of self-expression do not extend beyond foot stamping and high pitched wailing. You idiots are supposed to be the pinnacle of Java developers. You are the rare few who have the honour of leading and guiding the rest of us. You hand us specs to follow and be bound by for years to come. For fuck’s sake, don’t squander what little respect we have remaining for you. Set an example of adult behaviour, and maintain that apparently elusive tone of professionalism. Become role models for us to respect and admire, instead of nominal leaders that inspire nothing but shame and cringing.
July 1st, 2004 at 10:40 am
F.I.R.S.T.P.O.S.T. !!
July 1st, 2004 at 12:39 pm
I think all this JDO vs. Hibernate stuff is defocusing the EJB spec. Sure, persistence is one aspect of the whole thing but noone is really paying much attention to anything else. Are we going to be stuck with second string technologies in all the other areas as a result?
July 1st, 2004 at 1:26 pm
If they had any balls, they’d hold an EJB-JDO meeting/competition at the gold club tonite and see who spends the most!
July 1st, 2004 at 2:45 pm
Actually during the BOF Robin Roos got up to the mike three time – he even moved around the room to the other side in a diversionary flank attack. His question to the panel about whether they would all come to the JDO BOF – I’m sure Gavin King really wanted to tell him to just F#%K off. Then after that some equally cartoony character got up and just said “we want some answers”. What are these guys on about?
July 1st, 2004 at 3:08 pm
Looks like its all politics.
The people who (violently) support JDO seems to have invested/built business based on JDO.
And they perceive new EJB spec is a death bell to JDO and all associated stuff.
(But Hani, is this ur blog?)
July 1st, 2004 at 5:05 pm
JDO vendors are in panic mode because their product becomes obsolete five minutes after the first EJB3 implementation ships. If I just bought an app server and it happens to have POJO-based ORM, why would I spend money on a standalone solution?
After the bankruptcies and mergers start, maybe the JDO people can start asking themselves why they failed to attract more than .01% of the Java market share over the last two years.
July 1st, 2004 at 5:28 pm
You mean people actually pay for JDO stuff?
July 1st, 2004 at 6:03 pm
jdo rules! i dont need some lame container to run it in and its already proved to be working.
And there is open source implementations of jdo but sometimes you do get what you pay for.
Yes i also think that this childish behavior is getting too much and recently the jdo people started to make much of the noise but they do have some good arguments.. but the ejb people started it and i dident see the ejb people come up with any good replys.. other than fud!
but hey if you want to pretend that ejb3 will save you all then go ahead.. i will wait and see what happens, but im sure if the groups talked together it would be so much better.
July 1st, 2004 at 6:05 pm
Clown Puncher: it’s obvious, and based on totally empiric statistics EJBs are rapidly losing marketshare.
July 1st, 2004 at 6:23 pm
LOL :-)
Indeed.
July 1st, 2004 at 6:39 pm
I can’t wait for this conference to be over. Never have I been around so many fat, lazy wankers, who is unable to walk in a straight line at a steady pace. No, instead they wander around aimlessly, periodically stopping and blocking the floor for everyone else.
And get a fucking hair transplant. All of you!
July 1st, 2004 at 6:54 pm
After attending a long fucking day of sessions relating to JDO, hibernate, Castor JDO (does anyone still use this worthless piece of shit), etc., etc. And how JDO and hibernate used with EJB, and every other perverse combintion that any of this shit can be shoved together (or can’t). I have discovered this all now bores the living shit out me. Infact am so fucking bored of JavaOne in general the only thing keeping through the day is to see how many middle aged, struts-coding idiots i can bluntedly ignore before I can finally escape this wretched pit of arrogant, selfcentered, irrelevant assholes.
July 1st, 2004 at 8:41 pm
I think the JDO crew and the JBoss crew use the same marketing department. Lots of steam, lots of flailing limbs, but you still never see somebody actually using either of it.
And really, if JDO is AllThat. What stops you people from using it? Just use it and stfu already. JDO _is_ supported by Sun, it’s a JSR, no? So who stops you from using JDO?
July 1st, 2004 at 9:50 pm
my bald patch stops me from using jdo. it speaks to me and says ‘use hibernate’. i must obey or it will take over all my head.
July 2nd, 2004 at 11:06 am
It’s almost as if “EG” should stand for “Emotional Group” instead.
After all, very few of them are experts on anything–rather they are a bunch of emotionally charged tossers so married to their pet concept that they become more close-minded to the point of refusing to listen to anything else–validity of the alternatives notwithstanding. And if there’s one truth here, it’s that great solutions to problems don’t come from close-mindedness.
So, I for one, am looking forward to yet another slew of mediocre APIs. Which is just as well, because the best solutions to problems often come at times like this–when someone steps forth to woo the disenfranchised.
July 2nd, 2004 at 12:50 pm
I really don’t know when “blantantly obvious” became acceptable English. I would like to do *my* part to extinguish its usage by here pointing out the definition of “blantant”:
1 : noisy especially in a vulgar or offensive manner : CLAMOROUS
2 : completely obvious, conspicuous, or obtrusive especially in a crass or offensive manner : BRAZEN
So, we can see that to say “blatantly obvious” is akin to saying “obviously obvious” – and we don’t want any of our large brained citizens to be caught saying something so silly.
July 2nd, 2004 at 4:53 pm
B. Rintoul,
“Blatantly Obvious” is a pleonasm used to overemphasize the offensive nature of what is obvious. It’s a fairly common usage in Modern English. If you search Google for it, it’ll turn up about 33,900 hits in the Web and 47,900 hits in Usenet.
The American Heritage Book of English Usage states regarding “blatant”:
If you use definition 2 from the Merriam-Webster Unabridged dictionary, it makes sense:
July 8th, 2004 at 12:47 pm
Rintoul, being so pedantic is hardly helpful when trying to communicate. Consider your own phrase: “I really don’t know…”. Isn’t the word “really” redundant? Couldn’t you simply say “I don’t know…”? Do you mean that your level of not knowing is greater when you “really don’t know” than when you simply “don’t know”?
September 24th, 2004 at 10:46 pm
This thread turned into another argument about trivial semantics. I had enough fucking english language nit picking when reviewing requirements today. Not one new requirement was identified nor were any existing requirements changed. What is the fucking point of it!!!! Waste of fucking time. And that is Blantantly Obvious.