Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


2013/11/11 Pedro <pedlino@gmail.com>

Marcello Romani wrote
And all that just to have a 64bit binary that would only give more work
and
no immediate benefit...

After this reply I hope anyone whining about Windows users being let
down because there's no 64 bit version of OpenOffice/LibreOffice shut
the hell up and start complaining to Microsoft. :)

Right...

Because all FLOSS projects that have 64bit Windows versions (mentioned in
this email
http://nabble.documentfoundation.org/64-bit-tp4081444p4082245.html that
some
users choose to ignore) are all run by stupid people who choose to have a
lot of work for no reason...


Read your own post: "a lot of work for no reason".
First, some of these projects *have* reasons to have a 64bit build. GIMP
can handle large and complicated images, and need to break the 4GB limit
(2GB really on default build). Other needs to handle large quantity of data
and might take advantage of new vectorizations instructions, etc...
Second, it *is* a lot of work. Even in the post you mention, there is at
least two project that kinda struggle with 64bit windows build: firefox,
where they are not really supported, and FreeCAD, which seems to have
dropped support for 64bit windows. It's costly to maintain program that
build for many targets, and cost is an issue with some open source projects.
And last, building a piece of software from the ground up and
maintaining/evolving a (rather large) project for that long are very
different. Here, we're not talking about writting code from scratch, but
you have to make sure that every piece clicks. Going back through *all* the
code to make sure that there isn't a pointer somewhere or an int there that
would suddenly break because some OS API expect another type of value is
indeed "a lot of work", way more than just writing from scratch.
LibreOffice might be a fairly recent project, but it's codebase goes way
back.
And again, all of the work needed to barely have a stable working build
would yield very little benefit. The code don't magically take advantage of
64bit code by just changing the compiler's target.

So, no, other projects didn't decide to have "a lot of work for no reason".
*Some* decided to have 64bit builds from the start, *some* decided to
revamp their code, *some* decided not to, *some* gave up on it. But in
every cases, ressources for such projects are limited, and focusing on
bugfixes and enhancement seems more useful than having a 64bit build for
what is, regarding LibreOffice, no reason.

-- 
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.