Live data from Hacker News

From Supabase to Clerk to Better Auth

blog.val.town

21–30 of 259 posts

Re: From Supabase to Clerk to Better Auth

#21
post #5

Earlier quoted context omitted.

Lol wut? you get all of your auth data in your own db in 1 cli command. You are not tied to any on db provider. On top of that you get hundreds of auth features like oauth providers (I use it to allow users to log in via google, apple, github) and the best part it's free. Not saying Supabase and Clerk are bad, but they cost money. With better auth you pay exactly $0 for all of this.

Or I could use a web framework that offers that out of the box, and its free and lives in my database, wherever I want.

I’ve looked at these auth providers many times over the years and I just don’t get the value. It takes me a couple of minutes to set up auth. Why would I want a dependency? It doesn’t help me with the hardest part which is configuring Google and Apple sign in stuff on Google and Apple. I just don’t get it.

Re: From Supabase to Clerk to Better Auth

#22
post #19

Hey, Bereket from Better Auth here. I started Better Auth to solve this exact issue for myself, and it later turned into a company. It always give me joy to just see others getting the same value from it :) There is a lot to work on, would love to know what we can improve

Do you think the complexity of auth in the browser, is because browsers don't do enough?

Re: From Supabase to Clerk to Better Auth

#25
You could almost call the comparison between Clerk and Better Auth unfair. One is a service and one is a library, apples to oranges. Any third-party service integrated into a stack is a liability, libraries as well, but to a lesser degree. It’s about time for more services to be replaced by libraries. Better Auth really shows how to do that imo, it’s a library that integrates on the frontend, backend, and database. This is why it’s so good.

Re: From Supabase to Clerk to Better Auth

#26
This is why I'm so thankful I went with Lucia early. They sort of sunset their library and replaced it with documentation (and some small utilities) for how to manage and host authentication for yourself. It's always presented as some big, scary thing you can't manage yourself, but I found that taking the week to learn how security and basic salting works, I was able to feel more confident about how everything worked.

Re: From Supabase to Clerk to Better Auth

#28
post #19

Hey, Bereket from Better Auth here. I started Better Auth to solve this exact issue for myself, and it later turned into a company. It always give me joy to just see others getting the same value from it :) There is a lot to work on, would love to know what we can improve

Do you think the complexity of auth in the browser, is because browsers don't do enough?

I think auth is complicated outside of browsers too. But browsers do make some things uniquely confusing, especially cookies and general security primitives are full of footguns

Re: From Supabase to Clerk to Better Auth

#29

Earlier quoted context omitted.

Or I could use a web framework that offers that out of the box, and its free and lives in my database, wherever I want.

What framework offers all those auth features OOTB?

ASP .NET Core, Ruby on Rails, Django, .... the list goes on and on... The ones that don't usually someone built a package that lets it happen.
Post reply on HN