George W. Cherry said:
Is the successor to Java on anyone's horizon?
Prentice-Hall published four of my books which
featured languages (now defunct) which I loved
and embraced--Pascal and Ada. While three
of those books sold very well in the early '80's,
they are now out of print and recently the MIT
engineering library "warehoused" two of them,
because they had not been checked out for a
decade.
I'm writing a new book, currently using Java.
http://sdm.book.home.comcast.net
By the time I finish it (2009?), will Java be an
anachronism like Pascal and Ada?
Nope, and here's why.
Pascal had designed in limitations that really made it difficult to do Real
Work(tm), so you had several dialects but no real workable standard for the
language. It was basically usurped by C in the 80's, which rode the wave of
several consistent implementations on PCs as well as being the backbone of
the expanding workstation market (ala Unix).
Ada, while a fine language, never had deep penetration. Notably because of
its complexity, which made porting it to the newer, smaller hardware,
difficult.
Neither of these languages developed the core base and vendor support that
really propels languages in the market place. Pascal peaked twice, first
when it broke through with Turbo Pascal, and then later with Delphi. Ada
never peaked at all save maybe in the Defense industry because of the DoD
mandates.
Java, on the other hand, is now an extremely popular language, which enjoys
several implementations across most every platform available, an ENORMOUS
amount of available source code, and a wide array of practitioners ranging
from the embedded cell phone market up to modern monster mainframes and
clusters.
The biggest problem you may encounter would be having to bring your source
code up to date to the then current version of the JVM. Unless some of the
whatever new features they add are extremely compelling to your work, you
need not ensure that it leverages every latest bell or whistle. Just ensure
that your code actually compiles and runs on a recent JDK for the time.
Java 5 (1.5) is just around the corner, but I can assure you that once it
gets finally released, in 2005, it can easily be a year before, for example,
the major app server vendors even validate their servers to run on the new
release. So, by 2009, we should be well into Java 6.
If you write against Java 5, and then make a quick run through to ensure
that everything is ok for Java 6, I think you'll be fine.
Java isn't going anywhere. It is simply getting more pervasive, faster, and
more accepted. It still has the wind behind it and I can't see anything
taking its dominant place in 5 years.
Regards,
Will Hartung
(
[email protected])