Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • as the CPAN front page is all bulleted lists...and that's precisely what the page extols as readable. If people can't read that, then that's, again, not our problem but theirs. You know the old saying that you can lead a horse to water but you can't make them drink. CPAN is still around precisely because it hasn't been over-engineered like so many other things in perl.

    P5 and P6 and Ponie and Parrot are all to the point where only people with tuits and clue can do anything so I suppose the only thing lef

    • No, if people can't read something on your site it is EXACTLY your problem. Websites should do everything possible to enhance the user experience.

      The mere presence of bulleted lists does not provide a 100 percent readable, usable solution. Consider that the items on CPAN, for example, are not all that different and can confuse people deciding which item they should select.

      When our users tell us they're having a problem, we can't just say "Oh, you're all idiots". Why have such contempt for users? All user feedback is valuable.

      In real world usability tests I've seen users stare right at something (yes, I do eyeball tracking) and still not see what's there in the way we presume they will. I've seen users mouse within 1 millimeter of the desired link in lists, and just retreat back and not see that item.

      Users aren't as stupid as we'd like to think they are, and there are improvements to be made.