?

Log in

No account? Create an account
datetime.perl.org - brad's life — LiveJournal [entries|archive|friends|userinfo]
Brad Fitzpatrick

[ website | bradfitz.com ]
[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

datetime.perl.org [Mar. 4th, 2004|09:19 pm]
Brad Fitzpatrick
[Tags|, ]

whoa. yes!

http://datetime.perl.org/
LinkReply

Comments:
From: sheehan
2004-03-04 09:48 pm (UTC)

stream of conscious

... i like ... :)

do the existing date/time perl modules suck or something?

--scott
(Reply) (Parent) (Thread)
[User Picture]From: ydna
2004-03-04 09:50 pm (UTC)

Re: stream of conscious

It's not that they suck (well, some do a little). It's that there's so damn many of them. Who needs six thousand ways to deal with time? Perl programmers apparently. Dave Rolsky is my rockstar for tackling this nightmare.
(Reply) (Parent) (Thread)
From: billemon
2004-03-05 06:29 am (UTC)

Re: perl's new slogan ...

There's More Than One Way To Date It.
(Reply) (Parent) (Thread)
[User Picture]From: brad
2004-03-04 09:56 pm (UTC)

Re: stream of conscious

Pretty much. Like ydna said, there are a lot of them, they don't play well together, they're not polished, and they're not written by people that really understand the time problem.

Timezones, for instance, aren't covered anywhere. Bullshit like this doesn't fly with me:

my @la_time;
{
local $ENV{'TZ'} = "America/Los_Angeles";
@la_time = localtime();
}

Which works because the C library can do timezones. And which (I believe) will only work correctly if the system clock is set to UTC.

But you can't ask Perl (before these modules), "Given this time in this timezone, what's that time in this other timezone?"
(Reply) (Parent) (Thread)