61–70 of 87 posts
Earlier quoted context omitted.
> I’ve seen this game plan often enough. I probably haven't been around as long as you. Could you provide an example of one that comes to mind?
Auth.js: Vercel hired the lead dev and it stopped improving, leading to better-auth
Earlier quoted context omitted.
I interviewed for an SRE position at Auth0 years ago. My interviewer told me it was all held together by duct tape and prayers. I'm glad I didn't end up taking that position.
To be fair that's the views of SREs everywhere
Earlier quoted context omitted.
I don’t know the story, but I’m not surprised. I led an effort to switch my company to Auth0 recently and they’re… bad. They have very poor support for anything even barely outside of normal, and when things are working correctly they not very good. But when you have a requirement to move to a third party SaaS service, I suppose Auth0 is maybe the best of a bad bunch.
Auth0 went downhill after being acquired by Okta.
Better Auth has raised $5M. I don’t think it’s great to see a truly free project get absorbed into a commercial venture.
I've been using Clerk and it seems fine. I'm sure there's some drama, because everything comes with drama, but I just want to get on with building stuff.
Better Auth didn't take more than an hr to setup in my repo, which is already pretty bare-bones to begin with.
I really wish there was such an easy off-the shelf auth solution for Go
Earlier quoted context omitted.
NextAuth has supported delegating your db for years, companies like cal.com, deel.com and many others use that directly (not just for stateless jwt). I don’t really see the difference here, except that we handle more for you. And of course, If you don’t want to delegate your database, you can keep using NextAuth with stateless auth and we plan to add support for that as well. There are already many companies with lot…
Sorry for being dismissive - but I think that’s just a failure of imagination. Does every app using an adapter for Better Auth need to implement every plugin’s many thousands of operations, even if they’re only using basic functionality and a handful of operations? Auth.js differed in that you could let them handle it if you’re doing your low impact side product, but once you did care you can opt out. You’re telling…
No, and actually if you really really wanna override the core database calls, we have a way to do so. You just need to write a hook or custom plugin to override the `internalAdapter`.
> Auth.js did everything we need regarding authentication
I don’t think this is true. Any sufficiently complex project has had to add a lot of customization and logic on top of NextAuth to make it even somewhat complete. I was one of those people, which is exactly why I started Better Auth.
> auth in JS is in a sorry state
That’s been the case long before we started Better Auth, it’s the reason we built it in the first place. I hope we’ll be able to change that narrative. But I think what we already have is something other ecosystems can only wish for. Some references:
- https://www.youtube.com/watch?v=dNY4FKXwTsM - https://www.reddit.com/r/golang/comments/1le9q65/is_there_a_...