in reply to Re^6: Directory Syncer
in thread Directory Syncer

Yes, learning is a valid reason to reinvent wheels. It is not, however, by itself a valid reason to rely on the wheel you made. I've written my own CGI query string parser and my own templating system just like everyone else, but I've long thrown them away in favour of CGI.pm and the Template Toolkit. If I had the dedication to make a CGI module that's actually as good and as robust as CGI.pm, then I would make my own and keep using it. But I don't, and so I use CGI.pm because that's a known round and stable wheel.

Always have a good reason when you reinvent a wheel, and always have a good reason when you use your reinvented wheel. “Because I can” does not count among those.

(Not arguing with you, but clarifying my position.)

Makeshifts last the longest.

Replies are listed 'Best First'.
Re^8: Directory Syncer
by chanio (Priest) on Jan 03, 2005 at 03:19 UTC
    Well, a good reason would be to compromise at least a little with what you are using...

    When I read some critics saying that CGI.pm is now deprecated I realize that my first try of building my own CGI.pm was a good way of apreciating the good work done by professionals.

    CGI.pm is easy to use, and you don't have to think much, because it was all previewed by the author.

    It happens the same with a Hollywood movie. To make it look simple, clean and straight is not as easy as it looks. There is a lot to be polished, cut and replayed before presenting it to screen. Then it is easily understood even by kids.