40 years ago today, a children's TV show, which was to turn out to be very successful and educational to boot, debuted:
In Sesame Street's first season, the Educational Testing Service (ETS) reported that the cognitive skills of its young viewers had increased by 62%. They found that children who viewed the show the most often did 62% better at correctly recognizing a rectangle than less frequent viewers.
How long before we see a children's show teaching programming?
The only challenging part today was converting day-of-year to month and day-of-month. I'm not sure I got that 100% right (i.e. need to write more tests); also, I cheated a bit and disregarded leap years for now. I have a feeling this detail might undergo some change before the dust lands. Still, I like the feature (specifying year and day-of-year), and can see its use in some situations. It's valid ISO 8601, just as all the other datetime formats I'm implementing.
The reason I'm doing this work at all, is because I think the current way Rakudo handles dates and times is too bare-bones. I also think that adding a few convenience methods here and there to make it more useable out-of-the box — scratch that; I want to make it super-simple — is important, because most every semi-large application one writes will involve date and time. My argument boils down to not wanting to write
when I want to refer to April 1st, 2010. I'd prefer something like
(You think the former syntax is a joke? Go look at the Rakudo source!)
Update: and in no way whatsoever do I wish to blame mberends++, the chief author of Rakudo's current Temporal.pm. He's basically implemented things to spec... which is why the spec needs changing, too.