Re: DateTime::Lite

>2. it would mean different API
>3. as you say, it doesn't do everything DateTime can.
I want a hippopotamus for Christmas.

>1. it's XS
>   http://search.cpan.org/src/MSERGEANT/Time-Piece-1.13/Piece.xs
But it can't be vegeterian or live in the water.

Re: 3, #1 from your POD:
  (1) Target those who do not need the full feature of DateTime.pm
Except on the third Thursday of the month when the moon is full.
i.e; you have different claims for compatability requirements.
Also, #3 from your POD is specious.

Lite may pass the set of tests you extracted, but what about compatability
with DateTime extensions like ::Set? I contend that the best way to tackle
something like this and yield a more broadly useful "Lite" kit would be
to get DateTime to use AutoSplit and/or subclass DateTime to override the
chubbier bits. In my usage of DateTime, loading has never been the issue,
but rather things like parameter validation and lack of memoization
(friendliness).
-- 
Free map of local environmental resources: http://CambridgeMA.GreenMap.org
--
MOTD on Boomtime, the 35th of The Aftermath, in the YOLD 3174:
Niven's Law #17: No technique works if it isn't used.