X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2FCatalyst%2FManual%2FAbout.pod;fp=lib%2FCatalyst%2FManual%2FAbout.pod;h=74603c0964396c47e9984381ca9a087a2f73cd40;hb=d2132dd6b4a6588822e1eb29692095b619ce3ef5;hp=0ab2d6de3cbf1625b7615cc9fc8a3fc9cf11f39b;hpb=5e7073968974a588522d61b3a72b23cd87a8121a;p=catagits%2FCatalyst-Runtime.git

diff --git a/lib/Catalyst/Manual/About.pod b/lib/Catalyst/Manual/About.pod
index 0ab2d6d..74603c0 100644
--- a/lib/Catalyst/Manual/About.pod
+++ b/lib/Catalyst/Manual/About.pod
@@ -139,7 +139,13 @@ are automatically created when you begin writing a new application.
 Catalyst is not an out-of-the-box solution that allows you to set up a
 complete working e-commerce application in ten minutes. (There are,
 however, several systems built on top of Catalyst that can get you very
-close to a working app.) 
+close to a working app.)
+
+Catalyst is designed for flexibility and power; to an extent, this comes
+at the expense of simplicity. Programmers have many options for almost
+everything they need to do, which means that any given need can be done
+in many ways, and finding the one that's right for you, and learning the
+right way to do it, can take time. TIMTOWDI works both ways.
 
 Catalyst is not designed for end users, but for working programmers.
 
@@ -175,12 +181,15 @@ A variety of frameworks followed, of which the most widely used is
 probably L<CGI::Application>, which encourages the development of
 modular code, with easy-to-understand control-flow handling, the use of
 plugins and templating systems, and the like. Other systems include
-L<AxKit>, which is designed for use with XML running under mod_perl, and
+L<AxKit>, which is designed for use with XML running under mod_perl;
 L<Maypole>--upon which Catalyst was originally based--designed for the
-easy development of powerful web databases. Is it not the purpose of
-this document to criticize or even briefly evaluate these other
-frameworks; they may be useful for you and if so we encourage you to
-give them a try.
+easy development of powerful web databases; L<Jifty>, which does a great
+deal of automation in helping to set up web sites with many complex
+features; and Ruby on Rails (see L<http://www.rubyonrails.org>), written
+of course in Ruby and among the most popular web development systems. Is
+it not the purpose of this document to criticize or even briefly
+evaluate these other frameworks; they may be useful for you and if so we
+encourage you to give them a try.
 
 =head2 The MVC pattern