Ruby and PHP are easier for designers to learn and give them their first successes quickly. That's why they have prettier web sites in front of them. Maypole, Catalyst/Catamoose/Cata-what-have-you, Jifty, Mojo, or any other Perl framework you might be building next month are not going to make Perl more accessible to the brains of designers or give them their first successes anywhere near as quickly as Rails or PHP.
If I were going to try to get Perl into that niche, I'd think more in the direction of pushing something like Template to the point at which it can do everything a designer might want (database connections, sending email, etc.) without any need of serious Perl knowledge. Maybe from there the designers could be lured into learning Perl to do more serious stuff than the extended Template would be capable of. But the extended Template would have to be every bit as simple as Rails to get them that first success quickly.
It ain't about how pretty a Perl "website" [sic] might be. The pretty comes from the designers, not the language.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||