On Wednesday, September 18, 2002, at 08:41 AM, Erik Price wrote:
> > On Wednesday, September 18, 2002, at 08:59 AM, Puneet Kishor wrote: > >> It took a few days and the PHP community is already out with a very >> decent iCal parser. Reads ics files and makes calendars. > > The iCalendar file format has been around for a while, it is likely > that someone has been working on it for a while. yeah, while iCalendar has been around for a while, the PHP parser I believe is very, very recent. Here's the link http://sourceforge.net/projects/phpicalendar/ >> Perhaps the Net::ICal and related modules set out to do too much, and >> never got beyond the third alpha release. >> >> This is what bothers me... I want to do something quickly and I think >> of Perl... but I find it is sometimes just easier to do with PHP, and >> as much as I hate doing it, I concede another small "victory" to PHP. > > I think that a Perl or Python programmer is more likely to invest the > time in creating a true, reuseable module that can be used in many > different applications. Just the planning for something like this can > take a long time. Not to generalize about PHP programmers (though I > have been one), but usually the goal is very straightforward -- "get > this data into HTML format". Also, PHP doesn't have support for > modules in the same way that Perl and Python do, so this kind of > mindset isn't as prevalent. makes sense... but as a result PHP tools tend to be really simple to install and use right out of the box. And then they get more and more robust as folks work on them. For example, right now I have a rudimentary knowledge of both PHP and Perl. However, I can take the PHP iCal parser and start modifying it for my own use if I want to. I can't even dream of doing that with Net::ICal. I just want to take small baby steps, but the only vehicle available to me is _only_ capable of transporting me across the galaxy. > That said, I don't think that Perl is always the best language to use > for everything (maybe I and darn it, I want it to be. ;-) Cheers, pk/
