To be fair, memory footprint is a function and not a fixed thing. Java apps
take more memory than native apps as they pay the price for the VM and libs,
and this price may be big in the case of large libs that replace
system-provided functionality like Swing (in cases where the used lib is not
duplicating OS functionality, I would say the relative price of Java is zero
because a native app would also need an equivalent library). But it's a
one-time fee; in my experience, once I deliver that big cheque for creating
my first JFrame, memory use scales very nicely with application size.
----- Original Message -----
From: Nathan Meyers <[EMAIL PROTECTED]>
To: Mark Murphy <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, June 11, 1999 5:15 AM
Subject: Re: Newbie question: What is a footprint ?
> Mark Murphy wrote:
> >
> > I have heard this term used alot lately and was wondering if someone
could
> > explain to me what it is in reference to Java?
>
> A footprint is occupied space. A desktop PC's footprint is the number of
> square inches it takes up on your desk. An application's disk footprint
> is the space taken up on the disk by the installation. Its memory
> footprint is the amount of memory consumed in running the application.
>
> Java has a large memory footprint -- just running a trivial app eats up
> many megabytes of memory.
>
> Nathan
>
>
> ----------------------------------------------------------------------
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]
>
>
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
