By Kieren Diment
I have used Perl for roughly ten years, and feature adventure with all the "pre-Catalyst" frameworks and helpers (from CGI.pm to CGI::Application to dalliances with writing my very own and attempting Jifty). i have extensively utilized Rails and browse numerous books on it (most of that are disappointments).
Unfortunately, i discovered this advisor a unhappiness to boot. many of the e-book appears to be like based round a number of "examples," the biggest of that is a translation app from English into "Lolcat." the matter with such an app to illustrate is that it could possibly effortlessly be performed in a dead-simple, several-line CGI script (hell, even a one-liner may possibly most likely do it), so it calls for a definite suspension of disbelief that one may be utilizing stashes, chained dispatch equipment, templates, and so forth. Why no longer a standard CRUD variety app as an instance? dull, sure, yet to-the-point and prone to be illustrative of the instruments and their top applications.
The conversational "flow" of the ebook is distracting, besides. I remember the fact that a extra tabular or defined shape for making particular details more uncomplicated to discover may perhaps render it tough to learn "straight via" as a e-book. however the sheer quantity of knowledge, and variety of situations, make it not going that anybody will learn it immediately via and make equivalent use of all elements. much better to prepare the content material extra conscientiously via functionality -- for instance, the simplest and best-structured bankruptcy via a long way is the bankruptcy on dispatch (it will get to borrow for its prose constitution from the circulate chart on web page 168. much less in-depth meanderings into such adjuncts as DBIx::Class and Moose, yet extra on how (if in any respect) such open air modules needs to interface / play great with the Catalyst middle. A bankruptcy on blunders. A bankruptcy on logging. A bankruptcy on templating.
The index is a multitude and lazily prepare. less than "log", just one access: "Logging, in Catalyst, 7." (Are you critical? who wrote that index access? Logging, comma, IN CATALYST?!? SERIOUSLY??) For "error:" "error dealing with code, altering to output blunders to the log, 104-105." not anything for "exception" (fair adequate, as Perl effectively has none), yet less than Perl's identical, "die:" "die, utilizing for errors dealing with, 156." WTF? discovering those 3 sections is not an Easter-egg hunt. WTF will be mistaken with:
utilizing "die" ... 156
logging ... 104-105
see additionally *log*
log ... 7
mistakes ... 104-105
I'm rooting for Matt & co., and i am partial to Catalyst. yet this e-book wishes a remodeling for its subsequent version, and it wishes an editor (the typography, too, is underwhelming). it isn't that the staff that wrote this is not shrewdpermanent sufficient, or that they do not know the topic good sufficient. it is in simple terms that they should constitution, constitution, constitution, and make clear, make clear, make clear. anticipating moment variation, men.