Re: Abandoning Kylix makes Delphi less attractive?

From: pNichols (paul_at_computer-logic.net)
Date: 11/10/03


Date: Mon, 10 Nov 2003 12:42:14 -0500

Mike Swaim wrote:

> pNichols wrote:
>> BTW, what deployment issues are a concern with Java apps? I would
>> like to know what you think are problems with Java deployment, since
>> I do not know of any <G>.
>
> Which JRE you have installed comes to mind.
>
> --
OK, I thought you were thinking in terms of Java being like the current
state of DOT.NET for xplatform deployments (or even as difficult today as
NET for Windows deployment).

The problem many are going to have (if they are truly thinking that NET is
their future for xplatform development), is that NET is incompatible across
vendors. Mono of course, is currently the only NET implementor on any
platform other than MS, and in the docs for Mono, you will note
incompatibility issues (http://www.go-mono.com/faq.html#novell) between MS
NET and Mono NET. Look at the GUI section under this URL, alone will
demonstrate known compatibility issues. Other compatibility issues can be
found under the FAQs as well.

In addition, Mono is incomplete and it will be difficult for them to keep up
with MS, since NET from MS, is totally closed to anyone but MS. This is
quite different from Java, which has over 120 companies who are part of the
JCP. Fortunately, Javasoft now allows individuals and the Open Source
community to be able to suggest and develop for the JCP. The JCP
stringently enforces total adherence to the Javasoft standards so that
incompatibilities or deviation from the standards, will not be approved.

In other words Java is Java, despite the platform or the distributor. All of
the APIs are consistent, according to versions, across the platform and
distributor space. IBM's JDKs does not change my code if I developed using
Sun's JDK, nor if I use Blackdown or whatever.

JRE versions are an issue, but as long as you progress up (say from 1.2 to
1.4), then you would be OK. Of course, Sun has made this pretty easy now
(see the www.java.com site), and with Web Start, it will auto check the
user's workstation to make sure that the correct JDK would be installed to
match the deployed version specifications. Web start will also auto update
applications deployed to a user's machine by checking for new versions of
any libs or class files of the application being launched in a background
thread. This makes deployment and roll out, much, much, easier.

Distributing Java applications is a no brainer, in terms of deployment
across platforms (Unless of course, we are speaking here of server based
applications, where you are running EJBs, JMS, etc). For applications and
applets, simply packaging the application in a jar file, with all
dependencies included, means the entire application or applet is
self-contained. No registry worries, no directory here and directory there
dll worries, all dependencies are self-contained, whether running on
Windows, Mac, or Unix/Linux. Typical Browser based applications (not EJBs,
JMS, mind you), are a war file away from distribution. Jar packaging makes
Java deployment a real no brainer. Much easier than Kylix apps were to
deploy and even easier than all but the simplist Delphi ones.



Relevant Pages

  • JavaFX: dead on start?
    ... I was reading the slide presentation of Java FX at this URL ... Towards the end the slide says this about deployment: ... applications on the desktop, ... the JavaFX 1.0 SDK, which displays your applications as they ...
    (comp.lang.java.programmer)
  • Sun to host Online Live Q/A Conference on Java Application Deployment (WebStart) tmrw March 1st(Boyc
    ... Some of you are familiar with limits of applets. ... But deploying Java, applets and applications over ... The lead of Sun's Java deployment team and usability experts (Mike ... MacroMedia and MS Longhorn also have RiA kits, ...
    (comp.lang.java.programmer)
  • Re: Talking more about JRuby
    ... deployment of Rails applications on JRuby. ... mongrel from MRI, however, I'm not a Java guy. ... and warbler but I am not sure which I should be using. ...
    (comp.lang.ruby)
  • Re: Setting up JBOSS 5 Server on my local computer
    ... Source for Java: ... JSP deployment: ... Subdirectoried resources may differ between source and deployment. ... Note also that this does involve putting all your web documents in one or more directories under the root, rather than right in the root. ...
    (comp.lang.java.programmer)
  • Re: Rich Java client deployment options
    ... > I'm working on a system for deployment on a corporate network. ... > would like to use a technology like Java Web Start to take care of the ... whether the native compiler is actually capable of compiling your "rich java ...
    (comp.lang.java)