Much of what I say here Brent already said.
At 17.22 -0700 2000.06.14, Madeline Schnapp wrote:
>1. Java will have increased penetration into the "enterprise" computing
>environment.
Perl is already there, and will continue to be used more than Java.
>2. Access to information will become more fluid as the limitations on
>bandwidth become a thing of the past.
Sure.
>3. More and more applications will be hosted via applications service
>providers (ie. ecommerce backbones, financial processing, etc.).
Maybe.
>4. The move away from exclusive use of the desktop PC and to wireless devices.
Yep.
>The article states that Java is wonderful because:
>
>1. WAP compliant. Sun's wonderful revolutionary technology called J2ME,
>Java 2 Micro Edition was developed using WAP technology. The claim is that
>with this standard, Java will become one of the most ubiquitous programming
>languages in the enterprise, on a par with NT in terms of its install base.
Almost any language can do WAP. It is a very simple, basic thing.
Java has no special advantage here.
>2. Small Size. Java's small size and write once/run anywhere nature makes
>Java ideal for WAP platforms.
Java RUNNING on a WAP device? Java is SMALL? On what planet? Java
is big and slow. It is not going to be running on your cell phone in
the near future. It is for the server, like Perl.
>3. Compatibility. Server-side Java programs can be run on any type of
>hardware which allows enterprises a great deal of flexibility when it comes
>to hardware choices.
Perl can run on more types of hardware, with a higher level of
compatability/portability across the platforms.
>4. Large distributed programming environments. Java is ideal for large
>distributed development environments where many programming teams are
>developing pieces of large programs that are "glued" together.
That is a matter of taste. If everyone likes Java, then that's fine.
If everyone hates Java, then it certainly is not an ideal choice for
these programmin teams. Pulling programming teams together like this
is a matter of managerial prowess, not programming language choice.
>5. Security. Java security is built into its architecture. Wireless
>applications will require the ability to down-load code updates,
>necessitating extreme security. Of all the potential programming
>languages, Java is the most secure.
Well, Perl is the only language with built-in data checking for
tainted data, as Brent said. Java DOES have some more-or-less
built-in checks for downloading data from trusted sources, which Perl
does not have (the apparently abandonded Penguin project was to be
used for this). But since Perl will not be used on the client side
anyway, this is not somewhere Perl would be used.
But as noted above, I don't think many cell phones will have Java on
them any time soon, either.
>6. Infrastructure. Java has a strong enough infrastructure to build out
>large distributed systems. Built-in multi-threading networking, and file
>input/output make Java the best choice for quickly building network-enabled
>applications.
Java is slower at I/O than Perl, I believe. It certainly seems so on
all the PCs I use. Maybe on a SPARC it is different.
>These advantages, when combined with Enterprise Java Beans
>(EJB),
There are far more useful Perl modules than JavaBeans out there, from
what I can tell.
>allow the enterprise to create large distributed systems with far
>less effort than with comparable technologies.
I am not sure what they mean by "distributed systems". Probably just
picked it because it sounds good.
>7. Reusable code. EJB can be reused or bought from developers for faster
>deployments.
CPAN.
>The article concludes with the following:
>
>"Java will soon make major inroads into the enterprise marketspace.
Why hasn't it done it yet? It's been around long enough.
>Businesses need ways to improve efficiency and streamline all of their
>processes, and Java is one of the only technologies on the horizon that has
>major potential for solving these problems. Simply stated, Java is what
Perl already IS solving these problems.
>will drive the next generation of enterprise computing".
I'd rather take up truck driving than have to program in Java all
day. I have more important things to do with my time than write:
URL url = new URL("http://foo/");
URLConnection sock = url.openConnection();
BufferedReader bin = new BufferedReader(
new InputStreamReader((InputStream)sock.getContent())
);
--
Chris Nandor | [EMAIL PROTECTED] | http://pudge.net/
Andover.Net | [EMAIL PROTECTED] | http://slashcode.com/
