Has there been any rigorous discussion of why Rails doesn't have baked-in authentication? I've seen a handful of posts alleging that "authentication varies too much" but I'm having trouble envisioning which fundamentally distinct use-cases would prevent a single library from solving 98% of user needs.
Can anyone point to such a discussion? Failing that, I'd like to hear about various use cases which would be incompatible or messy if they were implemented in a single library. Being an 'opinionated' framework, it seems like authentication is something that would benefit from an opinion. -- 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/1689ec65-8a1d-4e94-a102-11fcda6ea464%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
