CHI looks a lot like Cache. From what I can see though it's goal is abstracted (by that I mean, "any" type of caching through this module) caching? Is this close to correct?

I appreciate the to the point-ness of this thread, my big issue has been digging through all the cruft of "advice" I've found in the past.

I agree in total with regards to Catalyst being a url->method call mapper. My question was geared more towards advice as far as spending time on creating my fairly completely customized code library or keeping it more general and using "standardized" things that are CPAN approved and such, if that makes any sense. I think it would probably come down to the needs of each application, or at least an average of each application's needs, so as to incorporate all that is needed. I doubt that will be something that anyone can answer one way, but I'm by no means a well versed web developer and I want to make sure my practices become practical and not detrimental to my work and building bad habits in the future.

UPDATE: Durr, of course CHI looks like Cache::Cache. It's intended to be an evolution of it.

I'd also like to clarify what I meant by migrations, and I'm sure I'll find something on here to do the dirty work that I'm speaking of, but I'm quite intrigued at how there's not much SQL directly involved in Ruby on Rails migrations and not having to open up a database editor and get dirty with SQL. God knows I love SQL, but I can only do so much at once without throwing things across the room. Hopefully this clarifies my wants a little

meh.

In reply to Re^2: speeding up web development by stonecolddevin
in thread speeding up web development by stonecolddevin

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • 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:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.