Great review! ++
The Cat gang embrace TIMTOWTDI to an extreme. TIMTOWTDI is great, but for newcomers, some recommended practices / examples would be helpful, esp. on the topic of structuring an app (directories and actions) and M-V-C design strategy.
I wholeheartedly agree. When I first started playing with Ruby on Rails, I immediately started to see some (much, even) wisdom behind their "convention over configuration" approach. Essentially, it's like building best practices right into the framework. You can do something differently if you want, but it's not usually in your best interest to do so. Then again, Rails is in some ways less flexible than I'd like, particularly when you have to work with an existing database. So, I don't think either framework has really hit the sweet spot on that issue. Making Rails more flexible may be harder than adding convention to Catalyst though, so that's probably a win for Cat.
-sauoq
"My two cents aren't worth a dime.";
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
