Isn't it time to build a plugin the allocates memory dynamically???
Isn't it time to let go of the idea that Java needs to have
the amount of memory an applet is going to run in specified
at startup time?
Isn't it time to construct a JVM/Plugin that will allocate
memory dynamically on an as needed basis like every other
piece of software on the planet?
First, there's the default limit that is imposed on applets
of around 96meg or less. That's not a lot of memory to start
For example: right now I'm most interested in panoramic
photography and publishing panoramas on the web. A more
or less middle of the road size for a pano is around
5000 x 2500 pixels. That only gives adequate resolution
when viewed in a browser by a pano viewer. Pano viewers
generally will take a viewport of between 600x400 to
full screen size to show a portion of that picture.
At 24bits plus alpha channel for 32bits per pixel you
get 5000 * 2500 * 4 ~= 50 meg. Then you have what ever
over head the viewer applet takes up and you are real
close to the default memory limit. And if you want to
do something clever like enable hot spots to link to
other images or web activities like sound. Or to just
load another pano of equivalent size -- the memory limit
gets closer and closer to causing your applet to fail.
My little applet fails all the time if the pano I try to
load is too big. That's not real good for business!
But you can get around that by setting the java_arguments
in *MOST* browsers if you are running plugin2.
So we have a limit but we can get around it. But if you
don't your (my) applet can fail. But you can't depend on
being able to set a higher memory limit than the default
limit of 96meg because not everybody is running plugin2
in a browser that supports the features of plugin2.
Which begs the question of why have a specified limit at all
that is guaranteed to cause some applets to fail?
Flash doesn't demand the programmer to specify the amount
of memory it runs in. I don't know of a single, widely used
program that does require the amount of memory it will run in.
The whole idea is a throwback to the 1980's when computer
memory was significantly smaller and much more expensive.
You can buy a gig of memory for what $50 - $60??? Consumer
grade computers come with 1 or 2 gig of memory. And huge
disks for virtual memory. Netbooks have 1 to 2 gig of
But Java applets -- you get 96meg -- one tenth to one twentieth
of the typical physical memory found on consumer level computers
and even less of virtual memory.
The memory limits on Java are about as necessary and modern
as a black and white television and a dial phone.
How about time shifting Java out of the 1980's into the