> There are a couple of advantages to using Java instead of Delphi.
> For one,
> you can replace
> class files without restarting your application especially simple with
> Inprise Application Server.
Yup, and you can load a class that you dont know about, eg:
Object something = Class.forName("mypackage.MyClass");
(then play with "something", which is an instance of MyClass)
> (sounds like an ad doesn't it! - yes i saw it at BorCon).
Works nice, and not just for IAS / BAS.
> I only use Java to create ports of a couple of my apps to run on my Palm
> Pilot. Java is still too
> slow for my liking.
I agree with GUI stuff, but not with server-side stuff. And its a lot more
flexable than most other languages (Delphi included), which is a fair trade
off in my books. If I can write a fast-enough, stable app in 2 days, vrs, a
slightly-faster, less stable app in 5, I'm going with the first.
> Although JBuilder 4 loads much faster than delphi 5.
With the right machine - forget it in less than 128meg. There again, Delphi
is getting close to needing 128meg for serious projects.
> No tool has killed Delphi although Delphi is not very popular in the US
> when compared to JAVA.
Blame THAT on the .com's.
> I don't think you will see a lot of desktop commerical type applications
> using Java (mainly because
> of speed - my opinion only...). Most Java apps are in house or for
> vertical markets.
Exactly. There again, so are 75% or so of Delphi apps.
N
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
