In a perfect world a solid gem would be extremely popular, well-documented, maintained and updated frequently, and serve a purpose that isn't short lived. It also needs to be flexible.
In the case of devise, it has few bugs and fits all of the criteria above. However, in terms of overhead, the type of project you are going to be working with may not require all of its features. Is it better to build your own authentication and understand every nuance of code you've implemented? Does it give you 100% flexibility? Certainly. But, make sure you know what you are doing also. It's one thing to be stuck in a black box and quite another to bury yourself in cement. -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-talk@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/a55f8374dfb716535f5451d30f734f3d%40ruby-forum.com. For more options, visit https://groups.google.com/d/optout.
