[Catalyst] So, what do we want in the -next- book?

[Jonathan Rockway]

* On Sat, Apr 26 2008, Ali M. wrote:
> i completly oppose another cookbook for catalyst
>
> catalyst need an indepth book that describe its design!
> the first book was very much a learning by example book, which is
> close to a cookbook
>
> and the main complain or the bad review where that, after reading the
> book, developers still didnt not understand how catalyst work (for
> exampl how subroutines attributes are used)
>
> we need a book with diagrams that exlpain the different pieces of catalyst
>
> a cookbook maybe be easier to write, but its not what i think is needed
> a cookbook is for people who already knows catalysts, this book trend
> will make catalyst a very exclusive framework only used by perl
> experts!

To be fair, the Advent calendar is usually well received.  People keep
asking the same questions again and again and again, which is why a
cookbook may be a good idea.  Instead of asking them, they can read,
understand the problem a bit better, and then cut-n-paste some code.
Not ideal, but the world isn't an ideal place.

Anyway, I hate to break this to you... if you want to know every detail
of how the code works, you have to read the code.  Reading code is the
most important skill a programmer can have, so I suggest biting the
bullet, opening up your favorite code browser (ECB++), and perusing.

Regards,
Jonathan Rockway

-- 
print just => another => perl => hacker => if $,=$"