You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by "Dennis E. Hamilton" <or...@apache.org> on 2015/11/09 01:12:03 UTC

64-bit AOO for Windows (was RE: [QUESTION] Usability of Non-Optional Java Dependencies)

I think the benefits of an x64 version of OpenOffice are understated.  It has apparently been worth it for a cousin OO.o descendant to provide one.  

I think there are two factors that favor having an OpenOffice x64 release:

 1. The biggest benefits of x64 builds are (1) optimized compiling for a more modern, high-performance instruction set and any multi-threading advantages that arise, and (2) ability to gain the benefits of much more RAM beyond the 3GB limit that applied under x86, reducing swapping and providing far greater input-output buffering.  I suspect (2) is the most noticeable, especially with large Calc files but maybe large documents too, although improved graphic hardware and software may matter more than we might thing.  There is also a benefit in using later Microsoft tooling at the same time, achieving possible entry into the Windows Store and using modern installer practices.

 2. I have seen justification of staying with x86 based on the fact that Microsoft recommends that Microsoft Office x86 still be used in preference over the x64 release to assure maximum compatibility with *existing* plug-ins and extensions.  I wonder if this is a red herring.  I have to assume that, since OpenOffice on Linux (including MacOS?) must match the bitness of those systems, that there has been no terrible difficulty around extensions and plug-ins being available/usable between x86 and x64 for those OpenOffice adopters.  Is that mistaken?

I also think that OpenOffice was limited in the past because there was no freely-available building of x64 applications with free versions of Visual Studio (i.e., the earliest Express editions and SDKs).  As far as I can tell, one can now produce x64 builds with current versions, including the free Visual Studio Community Edition.  Those editions don't produce x86 code for Windows XP very easily, but x64 is irrelevant for XP.  That might mean a different build for XP until one can retire XP support at some future feature release of AOO.  

> -----Original Message-----
> From: Andrea Pescetti [mailto:pescetti@apache.org]
> Sent: Monday, November 2, 2015 14:14
> To: dev@openoffice.apache.org
> Subject: Re: [QUESTION] Usability of Non-Optional Java Dependencies
> 
> On 01/11/2015 Damjan Jovanovic wrote:
> > 1. We don't have a Win64 version of AOO available for download.
> 
> This has never been a major request from our users, and also technically
> speaking the benefits a user would gain by running a 64-bit version are
> not so big. Sure, it look modern and it is good for marketing, and it is
> nice to have, but better OOXML compatibility (for example) would make
> many more users happy.
> 
[ ... ]


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org