So, how did he fare? Well:
- His “High Performance WebSites for dummies designers” book titled Speed Matters has been postponed to January 2011…
- …nor the “CSS for web devs” project.
The “Pattern” concept
There’s no major difference between the jQuery Cookbook and, for example, jQuery in Action. They both strive to be an all-covering go-to resource for jQuery development. But while the latter is cleanly organized and easy to use, the former is marred by the recipe concept, which sometimes seems to mean “very specific task”, and then in the next chapter it is suddenly synonymous with “this broad subject”.
As given away by the title, Stoyan’s book is organised in a similar fashion. Here, however, the mold fits the text like a glove. In no small part thanks to the fact that the author takes great care to define exactly what he means by “pattern”, what different flavours he considers the word to encompass, and how this applies to the structure of the book. In the case of JSP, the mold is not a populistic way to make it seem more accessible, but an honest and successful attempt to organise the information.
Also, Stoyan isn’t a slave to the structure, and doesn’t feel forced to include the word “Pattern” in every headline. When he sees the need to break the mold he does so.
How VS why
Also, a proper pattern collection / cookbook would probably be more like a phrasebook - serving finished solutions without explaining the nuts and bolts, and thus be of little interest to people actually wanting to learn the language. I’ve always shunned such books, finding that I have shorter journey if I take the time to equip myself first with an understanding of the basics.
And that was my fear - that the book, like the articles (and OOJS, to a degree), would list the different ways to create an object / emulate class inheritance / bind a function to a context / etc, without providing discussion or meaning. But, as previously stated, JSP is very different from the articles. Stoyan gives ample room to discussing the why, and all (well, most) patterns are defined with a clear goal and a problem space. We’re not simply being told “42”, but also what the question in question actually is.
Here’s a few comparisons between JSP and some other tomes you might already have:
The bottom line