Re:Essential Tools for Starting a Rails App in 2013
by aantix on Monday September 16, 2013 @01:33PM
(#6394475)
About 10 years ago, I remember a guy that interviewed that bragged that he wrote his own linked list class instead of using the one the STL used.
I was amazed and impressed at the time. Now that same statement would totally set off red flags and he'd be a non-hire (unless I could personally audit the code).
Maybe he provided more syntactic sugar so his implementation was easier to work with? And if that's the case, why not just build on top of the standard implementation? But if he claimed a performance increase, is that for the general case or for some specific case he was coding for?
Deviating from the standard library is a bold claim that has to be backed up by a code audit.
I agree that Devise is heavy and hard to extend but when we're considering such a fundamental like auth, you have to have a pretty good reason to deviate from the time tested popular choices.
Maybe you can write a lighter auth class, but can you write a more secure auth class? If devise has a vulnerability, there are tons of other sites out there "watching your back" and could report the vulnerability. If you roll your own, how are you going to aggressively audit its security?