Joshua Smith wrote:
>The issue is that for those of us who need to make applets that "just work"
>for all users (like on e-commerce sites), the only setting that matters is
>the DEFAULT setting, which is too low on the Mac.
>
>The result is that applets that "just work" on the PC don't "just work" on
>the Mac, which is bad for everyone.
Granted, on every point, but you still won't be able to assume your applet
will just work.
Suppose that Apple changes the default at the next minor OS release,
10.4.9. All the people who upgrade to 10.4.9 will then reap the benefit.
However, all the people who don't update to 10.4.9 will still only have
64MB default. And all the people who can't run 10.4 at all, or don't run
it for reasons of their own, will not benefit from the change to the
default.
So even if Apple did fix the default in the very next OS rev, assuming that
you'll have more than 64MB is guaranteed to fail for some customers, and
for some time to come.
If you have to curtail functionality to run in 64MB, or dynamically load
components only after you've determined you have the space, then that's
what you do to run in 64MB. If you change the baseline to require more
heap, then that's your intentional decision to exceed the default baseline.
Admittedly, programming complex applets that just work is a real challenge,
so I don't envy anyone the task. The last time I had to deal with that
kind of design decision we shifted big chunks of functionality into
servlets, which simplified the applet considerably. YMMV.
-- GG
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
