Hi Kind People! :-)
I have already written in the past about win64 builds. And now, after
reading this interesting entire thread I think:
- I completely agree that it is a first priority to complete the Calc
(LibreOffice?) code rewrite and modernization;
- but (!!!) just after this further rewrite (and not after the next
infinite ones!), I think (!) it will be useful to organize well the code
so that all Microsoft Windows 32 and 64 bit codes build automatically
and without any trouble (in my head this may be a big goal that may also
have positive effects in later time... like deprecated Windows API
cleaning, ...);
- I am 44 years old and I "am" in computer science since I was 16, I am
a computer science engineer since 1999, I have lived the 16 to 32 bit
Windows migration in the half 90s and I remember similar talks about the
priority to convert code or not (at the time not so much open source
(floss) one at least on Windows...) from win16 to win32s (does someone
remember these APIs?) or win32 (full);
- in that case, in 90s, the migration doesn't complain only the API bit
size, but a more fluid multithreading implementation, a native flat
memory addressing and so on...;
- now I suppose or try to guess (!), in particular on Windows systems,
we are in front of a similar API improvement/modernization that go
beyond the only bit size, data addressing size, memory address code
allocation (i..e. over the firsts 4 Gbyte), data size computation,
multicore suitable code, ...:
http://en.wikipedia.org/wiki/Windows_API#Versions
- I think that making intra-project experiences exchange (!!!) in win64
porting (and not only in this...) may put down time and money costs: The
Document Foundation are a XXI century Office Suite Management
innovation, why don't continuing to innovate the floss deploy also
formally exchanging experience without suffer to discover again (!) the
same things???!!! It is better to pay for the discover of the very new
things or ideas, isn't it?
- in the Document Foundation Wiki I have seen something about this
discuss, particularly about GSoC:
https://wiki.documentfoundation.org/Development/GSoC/Ideas#Porting_LibreOffice_to_x64_Windows
- below I build a little, absolutely not comprehensive, lists of already
win64 and only win32 floss Windows applications: are these first list
projects experiences useful to the GSoC student to reach our goal? I
think at least for most! ;-)
Already win64 floss application (All developers are genius? All projects
are petroleum or gold or energy rich? I don't think so...):
- Scribus (!!!);
- GIMP (already said in this thread);
- AviDemux (and developers have success over multi external library
porting; it depends on many famous multimedia libraries!!!);
- VideoLAN (and developers have success over multi external library
porting; it depends on many famous multimedia libraries!!!);
- Blender;
- Paint.NET (I suppose a simple .NET capability inheritance);
- FreeCAD (but there are some trouble in the building structure because
win64 builds are somewhat abandoned since a lot of months... It is a
very pity! It may be interesting ask them because and share experiences
so that we continue "never reinventing the wheel"!!! This possible
dialogue may be useful for both them and us...!!! And this approach may
push down develop costs...);
- BRL-CAD (recently!);
- RawTherapee;
- Ghostscript;
- Mozilla Firefox (but only in the nightly builds, as already said in
this thread, even though flash and java plugin win64 build are stable
and running since at least one/two years);
- PostgreSQL database;
- MySQL/MariaDB databases;
- Python;
- Java;
- PHP (experimental, interesting read here:
http://marc.info/?l=php-internals&m=137002754604365&w=2 or from Apache
Lounge http://www.apachelounge.com/viewtopic.php?p=22259)
- Apache HTTPD;
- ...
Not yet win64 (still win32) floss application:
- LibreOffice (!!!) (and AOO, I suppose);
- FileZilla (!!!);
- Notepad++;
- InkScape (!!!);
- Merkaartor;
- OpenCPN;
- GPSBabel;
- Mozilla Thunderbird (some win64 builds in the past were done..., do
you remember http://www.mozilla-x86-64.com/? Recently a Customer of mine
reaches the 4 Gbyte mail folder file limit I suppose due to SQLite
limit, surely for bad mail management (I make him to "archive" mail per
year), many mails with big attached files, ...);
- pgadmin (PostgreSQL GUI admin client);
- GNU Utils (I recently use gawk in windows environment to extract data
from a digital marine echo sounder/fishfinder datalog file and create a
.gpx xml GPS track file);
- SQLite;
- ...
*I think we, all together, could do API upgrade.*
*This is, of course (!), not in conflict with TDF donations, TDF project
financing and other marketing or future growing things...*
Have All a sunny weekend!
Carlo
--
ing. Carlo Strata
-
via Botticelli 1/4
30031 Dolo - VE
Italia - Italy
-
tel./fax +39.041.822.0665
cell. +39.347.85.69.824
Skype carlo.strata
Google carlo.strata.69
-
carlo.str...@tiscali.it
PEC: carlo.str...@ingpec.eu
Il 09/11/2013 14:35, Tanstaafl ha scritto:
On 2013-11-08 5:28 PM, Pedro <pedl...@gmail.com> wrote:
I know and I agree, Miguel. I just don't agree with the logic "don't
ask for
a 64bit version because it's very time consuming and expensive and
you don't
need it anyway".
Why do Linux and Mac people need it more than Windows people?
They don't. If you had bothered to actually read the responses in this
thread, you would understand that compiling 64bit versions on Linux is
*trivial*, and on OSX *much* easier than on Windows.
The reason there is none is because it is *hard* to do - *very* hard -
and because the benefit is so little, it isn't a high priority.
Yes, you are within your rights to *ask* for it... but when you start
demanding someone else do the heavy lifting for FREE, you begin to
sound like little children banging on the table that 'I want what I
want when I want it!'...
Do they work with files larger than 4Gb? Isn't the cost per developer
hour the same? If there is no advantage why do developers bother at
all?
READ THE DAMNED RESPONSES AND STOP WASTING EVERYONES TIME
--
To unsubscribe e-mail to: users+unsubscr...@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
