Given that this is entirely a dev-mode dependency, not a deployment-time dependency, I'm frankly not overly worried about that sort of thing...  Also, one minor win on that point would be to use platform specifiers to pare things down a bit:

```ruby
gem 'rb-fchange', :require => false, :platforms => :mswin
```

Not a huge win, but one less gem for those of us not on Windows.  Unfortunately there aren't any platform specifiers to winnow things specifically to OSX/*BSD or Linux as far as I can tell.

Also, right now there's two versions of rubypants in use:  The gem is used by `plugins/pullquote.rb`, but `plugins/rubypants.rb` provides a separate implementation.  Personally I favor not reinventing the wheel but either generalizing `plugins/rubypants.rb` so `plugins/pullquote.rb` can use it or changing `plugins/rubypants.rb` to use the gem would be tidier.

The current HEAD of the 2.1 branch has 57 gem dependencies in total, which from where I sit is not particularly worrisome.  For reference, a real-world Rails app I work with has 232 dependencies.  A high-security app I work on where we're very conscientious about what we add in has 66 gem dependencies.  More important than the number, I think, is the actual size of those gems:  For the afore-mentioned Rails app it's 197MiB and for Octopress it's a comparatively svelte 55MiB.  The smallest non-trivial app I work on -- which doesn't even involve a web server/framework in any capacity --  is 36MiB.