3 ms·

Parent is talking about the time it takes to integrate multiple ways to login, and I agree with him. When you implement only one way (be it social login with Go

Parent is talking about the time it takes to integrate multiple ways to login, and I agree with him. When you implement only one way (be it social login with Google/Facebook/etc or an email/password combination depending on your target audience) it's usually easy. When you have multiples ways to login, you end up having to (1) maintain more code, but also (2) need a way to reconcile users who end up signing in with multiple methods.

smaudet 9y ago
'Maintaining more code' is code for 'I can't write code/I am drowning in unrelated problems/I am just plain lazy' Its a fine philosophy to apply to an entire project where you may talking tens of thousands of lines vs thousands vs hundreds. It doesn't apply to a situation like this, where you are talking perhaps a few hundred lines, tops. If you are doing it right, I wouldn't think you are implementing much more than a thin wrapper around an existing login provider. There are so many valid open source implementations of this out there, this should be zero issue from a maintainabilty/testing perspective.