Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Java to die in 2003

Re: Java to die in 2003

From: Tim X <timx_at_spamto.devnul.com>
Date: 29 Dec 2002 17:52:15 +1100
Message-ID: <87d6nlmi5c.fsf@tiger.rapttech.com.au>


"Vladimir M. Zakharychev" <bob_at_dpsp-yes.com> writes:

> Well, that's just my personal attitude - I dislike everything that is
> unnecessary complex and basically denies KISS principle. J2EE
> is just that sort of technology - it is very complex, and it applies
> the requirement for complexity to everything you do. Just look
> how complex it is to maintain persistence in a BMP bean (or even
> in a CMP one, though it's much simpler) and how much additional
> classes are needed, and how much additional work they do for a
> simple task of storing and retrieving a row from database table...
> And this inherent complexity is everywhere in J2EE... But sure it
> gives J2EE developers a good opportunity for excellent earnings
> (and for hardware makers too, because you certainly need very
> powerful and expensive hardware to run these J2EE monsters...) :)
>

While not disagreeing 100%, I think Oracle is also a complicated beast, but like J2EE, it is only as complicated as you need it to be. At first, it might be a bit hard to wrap your head around all of it, but you can do a lot very simply and when you really do need some of the advanced and more complex looking facilities, you often find its a lot simpler using J2EE than do it all in some other language which does not have all the features and where you have to do it all yourself.

In fact, my biggest complaint with J2EE is that it makes it far too easy for developers to create applications which are more complicated than is necessary - there seems to be this belief you HAVe to use all the features all the time, even when your application does not need the added complexity. There also seems to be this constant push to use java solutions when much simpler solutions would do - the pervasive attitude that java can be everything and do everything and SHOULD be used for everything is IMO wrong. Its like someone using oracle simply for an address book - once working, it will be a very good address book, but do you really need something as powerful if all you want to do is manage a few addresses?

Just my $0.03 worth (bloody AU dollar!)

Tim

-- 
Tim Cross
The e-mail address on this message is FALSE (obviously!). My real e-mail is
to a company in Australia called rapttech and my login is tcross - if you 
really need to send mail, you should be able to work it out!
Received on Sun Dec 29 2002 - 00:52:15 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US