4 ms·
The issue I take with this stance is that people reading will put auth in the "too scary to implement" bucket mentally, and think it's fine to pay the Auth0 tax
by mattgreenrocks 2y ago
The issue I take with this stance is that people reading will put auth in the "too scary to implement" bucket mentally, and think it's fine to pay the Auth0 tax on every single project, even one with a few users.
This is a great resource to learn how to write it yourself, and things to take into consideration: https://lucia-auth.com/ https://lucia-auth.com/
IMO, this is one thing to implement carefully if need be (vs avoid altogether, as is the case of cryptography).
- wutwutwat 2y agoI should have clarified, I wasn't talking about third party auth SaaS providers, I was talking about auth libraries you'd use in your codebase. I also left "auth" ambiguous and didn't specify "authentication" or "authorization" because my original comment applies to both imo.