John Bokma wrote:
> The Spanish Inquisition wrote:
>
>>John Bokma wrote:
>
>>>Have you ever used MIME::Lite?
>>
>>I have tried it, actually. I found the template method easier.
>
> So you gave up soon, and now create code that's hard to maintain for
> others. Yes, MIME::Lite takes like 10 minutes to understand, and yes, I
> know reading doesn't look productive, but pressing all those keys the
> whole day looks like a lot is going on. But no serious programmer should
> do what you did.
Sure, so I'm not a serious programmer. That didn't you take long to
figure out, did it? I guess ten of thousands of satisfied users and
mainatinable systems that run for years on years don't count. No, my
less-than-dogmatic stance on reuse of modules dequalifies me completely.
It takes all sorts, John. I may not be your idea of an ideal programmer,
but I know I have some qualities that many other programmers miss. I
know some people who are pretty glad I'm not like other programmers.
>>Not
>>only to avoid using the module but also because it allows me to store
>>prefab message templates in files
>
> Since you haven't checked out on MIME:Lite, you missed that you can do
> this to, I guess.
Possibly.
>>and have them filled in by the perl
>>mailer. Works pretty well for my purposes.
>
> Yes, you created hard to maintain code, not a big deal if it's your
> tool, but a big deal if others have to maintain it. Moreover, you missed
> an opertunity to learn a new module, a big loss IMNSHO.
You can't learn everything as every programmer knows...
>>>>I remember that time when I tried to move a script that used POE to a
>>>>different machine. Unfortunately POE wouldn't install on the new
>>>>system for some obscure reason. There goes portability...
>>>
>>>But is that CPAN/POE/Perl or the "other machine".
>>
>>Does it matter?
>
> Of course it does, you rant about CPAN but the problem is very likely
> the machine. How can CPAN fix the problems on your machine?
I'm not saying it should. I'm saying that dependance on complicated
modules may hurt me (and my coworkers) in certain cases. It's no-one's
fault in particular, but it's something to consider when you have to
choose between rolling your own and using someone else's work.
>>Not all CPAN modules are perfect.
>
> Never said so. But if everbody does it your way we get a lot, and I mean
> a lot, of less than perfect code that's extremely hard to maintain, and
> full of bugs. CPAN modules are not perfect, but if everybody uses them
> they can get better. If you find a problem or have a suggestion it can
> be fixed/added.
Agreed there, but hey, I never said I wasn't lazy.
>>Some of them are quite complicated
>
> If you consider a module complicated I hate to guess your Perl skills.
> Programming is complicated, period.
I consider some modules complicated. POE is a good example. It good
stuff but it depends on many other modules and I've seen it not-compile
on some occasions. I consider other modules less complicated and some
are downright simple.
I've nothing against using modules in general. Hell, who could be a
serious perl programmer without using and writing modules?
>>and won't compile in certain circumstances. These
>>circumstances can't always be avoided.
>
> But you can report them, or contribute for the free use (and huge time
> saver) the others give you, and help to fix the problem. Most modules
> are made in spare time, you can't expect everybody to have access to
> several set ups and make everything work so you can have a free ride.
>
> Contribute and make it grow.
Guilty as charged, I should do more of that. Unfortunately not all bug
reports are acted on or even reacted on, which doesn't always help with
motivation. Analysing what exactly is going wrong can be a lot of work.
>>>Reinventing the wheel by cutting off 4 corners of a rock is not the
>>>easy way.
>>
>>Cute. We're not talking wheels here, though. We're talking alternative
>>solutions to creating simple mail messages. Both solutions work and
>>both have their advantages. Sorry to have stumble on a dogma here...
>
> Yours has only an advantage for you, and maybe that advantage is based
> on misunderstandig since you sound like someone who measures
> productivity by the number of keystrokes/hour.
No, not exactly. Sometimes I spend hours polishing stuff until it's just
right and sometimes I just do it the quick way. Sometimes I reconsider
later and do it right after all. Pretty much the way most people work, I
guess... (but then again I'm not a real programmer eh?)
Gee, I always liked the relaxed attitude of the Perl crowd, whatever
happened to that?
Ximinez
--
Our three weapons are fear, surprise, and ruthless efficiency...
and an almost fanatical devotion to the Pope....
http://www.ai.mit.edu/people/paulfitz/spanish/t1.html