3 ms·
(author here) I guess I view Rails as a tool with which to get things done, and usually rolling my own login or auth system is not within scope of the work I w
by zrail 13y ago
(author here)
I guess I view Rails as a tool with which to get things done, and usually rolling my own login or auth system is not within scope of the work I want to get done. I'd rather just use something off the shelf and proceed with the itch I want to scratch. You also get the benefit of lots of eyes on that part of your code base, which means bugs get found and fixed more quickly.
- luikore 13y agoMy experience: it's incredibly easier to NOT use devise. I've wasted so much time reading and hacking devise source code, while the result is slower and more vulnerable than rolling my own. It does a simple job, but there are too much code to make it compatible with many rubies and operating systems and older versions of rails that I will never use.