× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: How can Java eat up 160meg of memory?
  • From: "Stone, Brad V (TC)" <bvstone@xxxxxxxxxxxxxx>
  • Date: Tue, 29 Feb 2000 16:54:22 -0600

> Several points:  First, the vendor probably figures that anyone using
> Java knows better than to use the M$ JVM.  This may be 
> elitist on their
> part, but is common knowledge in Java circles. 

This is pure crap from the consumer endpoint and another bad argument from
the java defenders.  If the vendor thinks the consumer knows what a JVM is,
then they're a pretty sorry vendor and should be writing utilities for java
programmers, not tools for consumers that shouldn't have to  give a squirt
what language the app is written in.

  Finally, the vendor probably advertises that
> their application is Java so folks know they are not tied to WinXX --
> folks know the app will run on their operating system of choice
> (including OS/400). 

That's a laugh in a half and another one third!  The product is "made for
NT" and "written in java."  Means 2 things.  
1.  It will only run on Windows.  
2.  We wrote it in Java because it gets IT managers, purchasing folks, and
everyone else who doesn't know what it is all "hot under the collar" because
its "new technology."

There's no denying that.  Again, it's the under-educated consumer that gets
worked up with "techno-hype" that loses in this situation.  The only person
that gains is the vendor of the product.

Saying your app is written in Java is like an IPO for a tech stock.  It
doesn't mean much when the chips are cashed in.

> There are abundant examples of Java meeting real world business needs,
> and if you want to program to use the 'net then Java is 
> quickly becoming
> the lingua franca. 
> 

So I keep hearing.  But the two client-server apps I've used (not these
little applets or "helloworld examples") are slow.  And one for sure is
unreliable.  And the applets on the web just make my web browser slow down
or crash.

I know it could mean that Java got into the hands of a developement crew
that didn't know exactly what they were doing, but then again Java is so new
that no one is an expert with it, and I understand that.  

No one wins with hype that can't be backed up.

My 3 cents.

Brad
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.