On several occasions I've been motivated to post a review or to vote on a review. In every case, my motivation was unable to survive the roadblocks of the "mechanism". I don't recall what the specific road blocks were. I just recall more than one way that the implementation showed me an interface to invite me to do something and then changed its mind and denied me. Having tried more than once to jump through the hoops to satisfy its login (and perhaps other) requirements, I have yet to succeed.

I don't even recall what the requirements were, but had they actually been "minimal", I'm sure I would have met them (having met registration requirements before). I won't dispute that the requirements are likely "small", but they have certainly been enough to stop me despite multiple attempts.

Perhaps I'm just an abnormally lazy or picky person, or something. Or perhaps the implementation has some room for improvement. I find requiring registration to add a review for a module to be a rather disappointing statement on the implementors' view of their fellow humans. *shrug*

We are Perl programmers - we are supposed to be lazy.

I've had exactly the same experience and remember just as much about the roadblocks. *sigh*

---

Perl's payment curve coincides with its learning curve.

This would then argue that the current system should be amended. That still doesn't argue for an entirely new system. Have you made the suggestions to the appropriate people?

-- Randal L. Schwartz, Perl hacker