32-bit JVM

[Joshua Smith]

It's worth pointing out that the lack of 32-bit JVM means that Google Chrome on Mac can no longer run Java applets.

This is not some "nice to have" in a lot of people's view.  It is a really huge, freaking deal. 

On Oct 22, 2012, at 7:34 AM, Henri Gomez <henri.gomez at gmail.com> wrote:

>> Hi all,
>> 
>> I think it's a case that more people in the community need to be
>> willing to help support the 32-bit Mac OS X builds for the long haul.
>> Henri is obviously supportive :-) - Heinz, I'm not sure you'd have the
>> time to commit to this as well? There probably needs to be a small
>> group of folks for that port to be well-maintained.
>> 
>> The sad reality is that 32-bit Mac is dying out, perhaps there are
>> specific mailing lists/communities that you can reach out to?
> 
> I provided patches months ago to bring back universal builds (and so
> 32 and 64 bits mode) but nobody care about them.
> I also sent core and reports of failure when using OpenJDK 7 with
> universal patches against some apps like Jenkins, no more interest
> neither.
> 
> 32 bits Mac JVM is dying because there is no interest for it.
> All others platforms will have 32 and 64 bits JVM, Linux, Windows,
> Solaris, but not OSX, it's sad but "c'est la vie".
> 
> If users/admins/customers need 32bits JVM for minimal memory footprint
> or just because they just don't need 64bits addressing/pointers, there
> is plenty of OS and Java VM implementations around where 32bits
> support is still available and officially maintained.