Re: Y2038 on PerlMonks

Replies are listed 'Best First'.
Re^2: Y2038 on PerlMonks by thomas895 (Deacon) on Jun 05, 2012 at 00:01 UTC
Well, obviously it survived. OP: The Everything core doesn't have to use the epoch seconds for date fields. I don't know what it does use, but dates can also be represented as 20120604T165834, for example. Frankly, I think it will be okay. Heh, maybe it won't even be around anymore by then or have been replaced with something more modern. I would actually be worried if they still used this exact code then. Update: s/epoch times/epoch seconds/ && s/date calculations/date fields/ ~Thomas~ `confess( "I offer no guarantees on my code." );`	[reply] [d/l]
Re^3: Y2038 on PerlMonks by jdporter (Paladin) on Jun 05, 2012 at 02:08 UTC
Actually, most of what PerlMonks/Everything does in terms of dates, it does using database dates. After all: Everything is a (database) node.	[reply]
Re^4: Y2038 on PerlMonks by cavac (Prior) on Jun 13, 2012 at 20:42 UTC
Everything is a (database) node which of course is the root cause of the sometimes rather abysmal performance of the site. Like so many other things designed in the height of the dotcom bubble, the idea sounds terrific. You know, "It doesn't work that well in the real world, but who cares about such small details. Just invest all your money in our company and we will 'somehow' fix it all." "You have reached the Monastery. All our helpdesk monks are busy at the moment. Please press "1" to instantly donate 10 currency units for a good cause or press "2" to hang up. Or you can dial "12" to get connected directly to second level support."	[reply]