• Sam Ruby: Ruby 1.9 Strings — Updated
  A useful explanation of some of the details of how Ruby 1.9 handles unicode
  (tags: ruby strings unicode)

Recommend this post:

It’s very clear from posts on the rails email list that there’s space for books that take the novice developer beyond what they learn in beginners’ books like Agile Web Development With Ruby on Rails. Those books will help you build your first app and get a sense of the structure of Rails but before long you’ll want to write code that needs to be reusable between models, or across projects, or to interface with services other than databases. The beginners’ books, by definition, don’t deal with intermediate topics. That’s the niche Ruby on Rails Enterprise Application Development sets out to fill, but sadly it doesn’t offer much beyond those beginners’ guides.

Based on the title, I had expected going in that the book would be mostly focussed on cross-systems integration such as the use of LDAP, web services (particularly SOAP), connecting to multiple and/or legacy databases and other topics often lumped together as “enterprisey” which push at the rails conventions or require them to be abandoned. In fact the book would be better titled along the lines of “Up and running on Ruby on Rails in a small business” as the application developed through the course of its chapters is very simple and doesn’t demonstrate much about Rails itself that couldn’t be gleaned from AWDwRoR or one of its competitors.

Where some may find this book most useful is in the attention paid to windows-based development and to deployment (where it focusses on unix-based systems). Most of the books currently on the market do touch on using windows, but the authors of this one clearly use it themselves and actually advocate the use of an IDE for windows development. If your tastes run to Eclipse on Windows, that may draw you to this.

Though the book references Rails 1.2.3, the application built inside could just as easily have been built on Rails 1.1. The app is CRUD-based, but there is no mention of REST or map.resources, despite the fact that they could have simplified it. Authors don’t have to buy into the prevailing wisdom in the rails community, but it’s a shame when strategies that can simplify apps aren’t covered.

Perhaps more worrying given that Rails 2.0 is now out the door and will be the default for anyone starting out with this book now is the use of deprecated techniques such as dynamic scaffolds (the scaffold keyword was removed 10 months ago in changeset 6306) and old-style pagination (which left in changeset 6992 back in June)

There certainly aren’t as many books out there for newcomers to Rails as there are for some other languages/frameworks, so its inevitable that more are to come. It’s a shame that already at least two such books have been pitched at intermediate developers rather than their more correct audience, and hopefully that trend won’t continue. It would also be very helpful if packt would publish an addendum to this volume detailing the aspects that no longer work in Rails 2.0. Missing some great new feature in Edge Rails is one thing, but it’s quite another to rely on features that were scheduled for removal over six months before a book goes to press.

Disclaimer: I was sent a copy of this book for review by the publisher. You can find it at packt, amazon US, amazon UK and all sorts of other places.

Recommend this post:

• Music in China: The Inside Story | The Register
  An exploration of the music industry in a very different culture. One striking anecdote: apparently the Chinese version of pop idol terrified the Chinese authorities because of the level of participation in its "democratic" decision making
  (tags: china musicindustry)
• BenCurtis.com » Painless Rails action caching with memcached
  One of a number of pieces building on Tobias Lütke’s suggestion that the best way to do cache expiry is not to expire a cache.
  (tags: caching memcached rubyonrails)
• sparrow - Google Code
  "Sparrow is a really fast lightweight queue written in Ruby that speaks memcached." — there’s a lot of conversation around messaging/queuing at the moment and this looks like a good tool
  (tags: messaging queuing ruby sparrow)
• About This Blog: Beanstalk Messaging Queue | Ruby on Rails for Newbies
  How one blogger is using a messaging queue
  (tags: beanstalk messaging queueing)
• stompserver’s stompserver-0.9.8 Documentation
  Another messaging server
  (tags: messaging ruby)
• Ryan’s Scraps: What’s New in Edge Rails: Pluggable Controller Caching
  It looks like caching is one of a number of areas getting nicely refactored APIs in Rails 2.1
  (tags: api caching refactoring rubyonrails)
• Best Authorization System Ever
  A high claim to make, but this does seem like a decent option for rails authorization systems
  (tags: authorization rubyonrails)
• MySpace.com : Earwig
  Myspace UK’s new attempt to profile "the latest picks of brand new talent". Shares the rest of myspace’s apalling design, though thankfully with less intrusive advertising.
  (tags: earwig musicpromotion myspace)
• BBC NEWS | Business | Warner agrees to use MP3 format
  Is the DRM camp finally packing up?
  (tags: futureofmusic musicindustry warner)
• Strike hiatus prompts Hollywod writers to go it alone | Special reports | Guardian Unlimited
  A number of Hollywood writers are looking to bypass the studios and self-distribute online. It’ll be interesting to see if they can find a revenue model to fund the production budgets they’re used to, but in many ways this seemed inevitable
  (tags: hollywood mediadistribution movies screenwriters strike television)

Recommend this post:

With PHP 5.3 looking very close to release, bringing with it significant changes such as namespaces, this is an awkward time to release a PHP book of any generality. Within a few months it will be clearer how well the new features are taking hold and there is almost certainly going to be a clamour for books that show how new features affect development practices and how to make use of them. Even without that, it is hard to recommend this book as it fails to live up to its promise and provides a poor introduction to Object-Oriented programming.

The book’s first problem is the poor quality of the English contained. The author does not appear to be a native English speaker and the publisher has apparently done little to clean up the language. For the most part that simply makes for some curious rhythm and phrasing but there are a number of places where it contributes to inaccuracies, such as constant confusion between objects and classes. Finding such inaccuracies alongside mistakes such as confusing polymorphism and inheritance I’m left wondering how well the authors really know their subject. Packt would do well to employ another reviewer to clean up the syntax and definitions before any reprints.

The structure of the book is curious. Rather than approaching topics through the use of an example project or projects, the author gives disconnected samples, often offering little beyond that which can be found in the online PHP documentation and generally failing to explain how techniques would be useful. While he insists that PHP5’s Reflection API is an important tool, there is little to back up that assertion. There’s a large code sample and a list of the methods and attributes of a reflection object, but no real substance. The database section covers some key examples, such as PDO, ADODB and MDB2, and touches on the ActiveRecord pattern, but uses four pages to list the RDBMSs that ADODB supports and then only spends a page and a half on ActiveRecord, failing to explain either its concepts or advantages in any detail.

The high point of the book is the half chapter on unit testing. A few well chosen examples provide a demonstration of how code can be tested and how that allows for refactoring without fear of regressions. The reasons for unit testing are clear as is basic usage of PHPUnit. I’d have liked to see further examples rather than several pages listing all the default assertions PHPUnit provides, and I disagree with the claim that there should never be more than one assertion per test (individual tests should focus on a single concern, but can use multiple assertions to do so) but by that point in the book it was good just to see a section that made its point clearly.

Fundamentally, I came away from this book feeling it had failed to communicate clearly the core principles or reasons for object oriented programming. By trying to cram in too much reference material, not offering clear contexts for each technique, and not lingering on ideas like encapsulation the book fails to instill OO techniques.

Disclaimer: I was sent a copy of this book for review by the publisher. You can find it at packt, amazon US, amazon UK and all sorts of other places.

Recommend this post:

• Josh Owens » Rails Edge Change: How to add a counter cache to an existing db table
  Counter cache attributes are protected in rails 2.0 so you need to use slightly different syntax to update them manually/in a migration
  (tags: countercache rails2.0 rubyonrails)
• BBC NEWS | Technology | Weblogs rack up a decade of posts
  We’ve now had 10 years (and a few days) of blogging, apparently.
  (tags: blogging)
• Premailer — preflight for HTML e-mail — dunae.ca
  Appears to do everything I was looking for in an HTML email toolkit
  (tags: htmlemail)
• Antisocial networking « Adam Greenfield’s Speedbird
  Interesting thoughts from Adam Greenfield — "I believe that technically-mediated social networking at any level beyond very simple, local applications is fundamentally, and probably persistently, a bad idea."
  (tags: adamgreenfield relationships socialnetworking)
• David Byrne’s Survival Strategies for Emerging Artists — and Megastars
  David Byrne reflects on the state of the music industry from artists’ perspectives, and chats with Thom Yorke
  (tags: davidbyrne futureofmusic musicindustry)

Recommend this post: