Thursday, October 18, 2007

Why Oracle's Middleware sucks...

"for a large company like Oracle, if your products are good, they can’t be great because there’s more risk in being great."

Does this tell us why, seeing their middleware products are poor, they daren't be mediocre? I can feel an award coming on.

Update. For what its worth, and in the interest of not appearing to just be a loud mouthed asshole, this comment on TSS reflects some pretty commonly held opinions of Oracle's J2EE container OC4J, and for those of you who haven't had the dubious pleasure of working with OC4J you should know that those of us who have consider that 10.1.2 is significantly better than 9.0.4 which itself was a huge improvement over the woeful 9.0.3, and 9.0.2 was just a joke. Little wonder then that the big O don't have many fans in Java-land.


Anonymous said...

I remember when I had to work with Oracle Portal 4 or 5 years ago. Man, THAT was a true "adventure". Of course it ran on 9i and OC4J. Since then, when I see Java code from Oracle I just do the one right thing: run.

blog comments powered by Disqus

I know nothing, I'm not a fortune teller, and you'd be insane to think that I am. This disclaimer was cribbed from an email footer I once received. It is so ridiculous I had to have it for myself.

Statements in this blog that are not purely historical are forward-looking statements including, without limitation, statements regarding my expectations, objectives, anticipations, plans, hopes, beliefs, intentions or strategies regarding the future. Factors that could cause actual results to differ materially from the forward looking statements include risks and uncertainties such as any unforeseen event or any unforeseen system failures, and other risks. It is important to note that actual outcomes could differ materially from those in such forward-looking statements.

Danny Angus Copyright © 2006-2013 (OMG that's seven years of this nonsense)