I must say that in the partially joking vein of my question I was quite curious to know what a "module that contributes to one's hubris" could be, even before knowing which actual modules people would suggest.

Indeed boasting with friends contributes to one's hubris, so any module that helps us writing software that we'll proudly show to friends is a good candidate. Unfortunately I can't think of very good example myself. Probably

• File::Find
• Proc::ProcessTable
• Digest::MD5
since afaict they're the ones I used most in small utilities I felt comfortable enough with to distribute to firends. (Well, if we exclude strict and warnings that indeed help me to write code I can feel proud to show off...)

With it, I never have to wait until being back online to install a module I find needed for something I want to do ASAP.

One that contributes greatly to my hubriness is Acme::Pr0n.

No, really :-) Like "See? This language I use even has a module for getting pr0nography of the web. Does your language have something like that?"

And they never say "sure", they just stay there, staring, trying to understand whether it is true, and then they start making questions on how to use it :-)

The combination of CGI and HTML::Template on the server side, and WWW::Mechanize and Test (soon to replaced by WWW::Mechanize::Test) on the "client" side contributes to my Hubris. Apps grow quickly, one functional test at a time.

When I'm feeling particularly bold, I'll even take two or three steps at a time. Woo hoo!

For Hubris, I would list all of those modules you'd have to pry out of the programmers cold, dead hands. Some modules get so wildly popular that they try to use them for everything no matter the task.

Without any judgement on the actual usefulness or quality of the modules, I think that list includes: CGI, Class::DBI, Maypole, CPANPLUS, WWW::Mechanize, and CGI::Prototype (hi Randal! How's Rio?).

I think a lot of the Class::* hierachy exists because the author thinks that if everyone just used his module, so many problems would just go away. In some cases that may be true, but it's still Hubris

For Hubris, I would list all of those modules you'd have to pry out of the programmers cold, dead hands. Some modules get so wildly popular that they try to use them for everything no matter the task.

On a totally unrelated (and OT) basis, this reminds me of when I first learnt the method of integration with residues: I found it to be so cool that I tried to apply it everytime, everywhere. And once I remind finding myself going mad trying to find a proper contour to calculate a definite integral - until I realized it was an elementary one!!

Without any judgement on the actual usefulness or quality of the modules, I think that list includes: CGI, Class::DBI, Maypole, CPANPLUS, WWW::Mechanize, and CGI::Prototype (hi Randal! How's Rio?).

Indeed at work we use Class::DBI and my impression is that it contributes excellently to all the three Virtues.

Well, I think that Virtues of Programming may include getting mad and happy, so I will say that sometimes I get mad with CGI, because there are so many ways to do things, but most of the time I am happy, as I can use CGI to do many things quickly ;-)

If that makes any sense.

I'm sure that there are many other modules like this though.

I'm not sure wether "getting happy" would be considered a virtue. Certainly it is an aim. Since you stressed that you can use CGI to do many things quickly, it certainly satifies your Impatience needs. As to "getting mad"...ehm...I really don't know!

To my way of thinking, modules that contribute to impatience and hubris would be ones that cause you to write more modules. Net::Server did that to me, and you might also look in the ExtUtils:: namespace.

Howdy!

Could you expand on that? I'm curious what about Net::Server motivated you (and in which way). I've used that module in the past, and need to get back to that project...so if you have something to say that might move me to consider alternative modules, I'm all ears.

yours,
Michael

Well, I kinda needed a custom POP3 proxy, and I wanted the flexibility to be able to do arbitrary nonstandard things with it (e.g., disobey parts of the RFC in carefully considered ways; for instance, respond to DELE requests by marking the message as having been retrieved by that user account already, if more than one account are sharing a mailbox (so I can play with new mail clients and still get my mail in the regular one)). But creating the whole server architecture and everything would have been a lot of work, and I never would have found a TUIT. But since Net::Server existed, all I had to implement was the POP3 protocol itself. Hence, Net::Server::POP3 was born.

---

"In adjectives, with the addition of inflectional endings, a changeable long vowel (Qamets or Tsere) in an open, propretonic syllable will reduce to Vocal Shewa. This type of change occurs when the open, pretonic syllable of the masculine singular adjective becomes propretonic with the addition of inflectional endings."  — Pratico & Van Pelt, BBHG, p68

For me, "Hubris" is satisfied by a nice platform-independent graphical interface. I use Tk.

For me, "Hubris" is satisfied by a nice platform-independent graphical interface. I use Tk.

Indeed I had thought myself of Tk. Unfortunately I am only slightly more than a beginner with it and I'm far from the boast-level. So definitely it can't contribute to my own hubris yet! :-(