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

Not quite.

this is a finite and and absolute wall dominated by the laws of the
universe in science and math, and cannot be fixed at all, unlike the
original Y2K date issue
Well... not really. See, the original issue was that years were only
stored as two digits, instead of the complete four. Those two digits
were added to 1900 to get the year. So after 1999, the two digits
didn't hold enough information to continue counting, and "wrapped
around". With this it's the same thing. A 32 bit number is used to hold
a number of seconds, and this number is added to a base
"epoch" (00:00:00 UTC on Thursday, 1 January 1970). After 03:14:07 UTC
on Tuesday, 19 January 2038, a 32 bit number won't be able to hold
enough information to continue counting.

Bottom line is ALL IT type of hardware and software, down to
Well, practically, probably about right. Theoretically some systems
either won't care about the date (like, well, calculators), or will use
alternate methods of storing a date (many software systems use a
date string, such as the ISO 8601 standard). But yes, lots of stuff
*will* be affected.

has to be changed to 64bit in it's entirety
Again, in practice, probably right. This is not the only solution,
there are others, such as date strings (which could be a solution for
many software systems), but for most systems (and especially hardware
systems) the only really practical solution is moving to 64-bit.

Sorry to bother, I'm sure you all already knew this, and Andrew was
just simplifying.


On Fri, 26 Jul 2013 19:57:23 +0200
Andrew Brown <> wrote:

Ah!, but we have to have everything!!!! digital wroking in 64bit
before the year 2036 and 2038.

As we of us that went through and were involved in the raw IT support
of the Y2K issue will know, which is a pimple on the back of a blue
whale, compared to the coming ultimate Y2K. From 2036 onwards
(non-Unix/Linux will be affected from 2036 and Unix/Linux from 2038),
this is a finite and and absolute wall dominated by the laws of the
universe in science and math, and cannot be fixed at all, unlike the
original Y2K date issue. Bottom line is ALL IT type of hardware and
software, down to calculators, mobile phones, tablets PC, aircraft
computer, whatever we use a computer to control and mange, has to be
changed to 64bit in it's entirety.

So LO and other like Office suites all will have to move to 64bit. We 
live in a universe bigger than man's current state, and we expose it 
incredibly in the digital world of ours today.

To help those understand what's coming and not letting me fill up an 
email, here are some links of good reading explaining this. There is 
plenty more about this out there.


Andrew Brown

On 26/07/2013 03:39 PM, Tanstaafl wrote:
On 2013-07-26 8:18 AM, Jay Lozier <> wrote:
On Fri, 26 Jul 2013 08:03:43 -0400, Tanstaafl
<> wrote:

On 2013-07-26 7:54 AM, James Knott <> wrote:
Tom Davies wrote:
My guess is that the default is 64bit or else other apps might
need the 64bit version.  It's generally not a good idea to have
more than 1
version of Java although even 1 might well be more than you
need now.

The big question is why are the Windows version of LibreOffice
and OpenOffice still 32 bit only.  They've both been available
in 64 bit versions on Linux for years.

Because there is basically no good reason to use a 64bit version
of an Office application - unless you really need to work with a
spreadsheet or text document that approaches 4GB in size

Even Microsoft recommends installing the 32bit version of Office
on 64bit machines.

The 4GB limit causes problems with databases moreso than a text
document or spreadsheet.

Personally I can't see using LibO for managing/working with
databases that big...

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.