> Since there is no more will_paginate in Rails 3, the only option is kaminari.
This version of will_paginate seems to be fine in Rails 3:
While I'm on the Rails 3 things you can find on Github topic, ActiveScaffold has a nice Rails 3 port here:
will_paginate may pollute Array, but it's been a great solution, that has worked for a long time. Be wary of upgrading for the sake of upgrading, especially with that kind of performance degradation.
Ruby Toolbox is great too:
Have had moderate success with https://github.com/NoamB/sorcery lately, however I'm not yet confident in calling this a solved problem.
edit: Devise is great for getting up and running quickly. For that matter though, so is Joomla.
If I were doing an app with standard model authentication, a Forum for example, I would use devise again in a heart-beat, but for any other project where I expect to have any slightly customized behavior at all, Ill be rolling my own.
Devise is brilliant if you want something straight-forward, but it is big, complicated (internally), and not very flexible.
Authentication can get downright nasty no matter which solution you use, but Devise does a lot of things well, is actively maintained, and well documented. In fact all of the gems from Jose Valim, including inherited_resources and simple_forms are such first rate plugins, it's difficult to imagine anyone throwing any of his work under the bus.
Sorcery looks cool. Thanks for the heads up.
(Also, it works fine with CanCan, which is brilliant and does a good job at staying out of your way.)
Geocoder's api feels a little bit more modern Geokit (rails3 vs 2). Having read the code for both, Geocoder was cleaner and would be easier to tweak if necessary.
So really it's just a preference: they do the same thing.
While I hope to eventually be able to pick which gems I like to use best, for a beginner this kind of guidance is really valuable.
I recently put together several detailed tutorials along with application templates that generate Rails starter apps using Devise, OmniAuth, RSpec, Cucumber, plus options for jQuery, Haml, etc. I loaded them up to my GitHub account and initially I was surprised at how many people were expressing appreciation and encouraging me to do more. Now I think I realize, it's not easy for many people to keep up with the ever-evolving Rails habitat. There's really a need for guidance that goes beyond the good intro tutorials and shows the steps need to assemble the pieces for real-world projects.
Here's a link to my GitHub account with the various example apps and tutorials:
The alure once was how quickly developers can build web apps. It seems to be becoming more limited to how quickly experienced Rails developers can build web apps.
The only thing that holds it back is the learning curve, wich is strange, because behind it is just plain rails philosophy: controller methods + views with a tasty DSL to plug them together.
A big thanks to Volker for his huge work on pushing it to rails3 compatibility.
The current rails3 branch (Volker's) it very stable.
What remains to be done to make it even more awesome is:
* use nested_attributes_for and clean the custom nested attrs logic
* clean security layer witch at the moment uses gobals (and can only be used in shared nothing deploy)
* request local configuration copy to make it more runtimeasible, at the moment it uses a class var (global-ish) that, for some customisations, needs to be altered per request, and that again leads to only-shared-nothing-deploy
* ActiveModel API so Mongoid can join the fun too
* a child gem that bundles AS to make a fully featured admin interface, competing with rails_admin & friends.
Side note: I wish the Rails team would take more of the Django approach and build some of these features into the core.