Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Better Auth – Authentication library for TypeScript

better-auth.com

Post reply on HN
Print view View original

21–30 of 37 posts

Re: Better Auth – Authentication library for TypeScript

#21

Post by aswerty »

aosaigh wrote: post #4

As someone developing with both Nuxt and Next, I find these "full-stack" JavaScript libraries and frameworks really confusing and difficult to grok. I understand the benefit of only having one ecosystem to worry about (JS/TS in Node and browser) but I'm not convinced that having backend and frontend in the same codebase is actually a good idea. It might be due to being a more "old school" full stack developer, but th…

100% agree with how confusing it all feels. Smudging data and code back together feels like a massive step backwards. I can't but be reminded of the disaster that was ASP.NET Webforms.

It took me a while to grok that in SSR frameworks, you shouldn't treat the SSR backend as a data backend. The best mental model is that the "SPA" just now has a client-server boundary in the middle of it. You should have a normal data API servicing the SSR backend.

With this approach, this does mean that client-server auth can now either live in the SSR backend or as normal on the data api. Arguably doing it on the SSR backend makes the most sense since that is now your server boundary. In this context the resurgence of auth in the SSR space make sense.

Re: Better Auth – Authentication library for TypeScript

#22

Post by fsndz »

oDot wrote: post #14
aosaigh wrote: post #4

As someone developing with both Nuxt and Next, I find these "full-stack" JavaScript libraries and frameworks really confusing and difficult to grok. I understand the benefit of only having one ecosystem to worry about (JS/TS in Node and browser) but I'm not convinced that having backend and frontend in the same codebase is actually a good idea. It might be due to being a more "old school" full stack developer, but th…

I am a big fan of Gleam language's Lustre[0], and due to its functional nature, the full stack experience is much better. Instead of becoming this mishmash of backend and frontend, there's a clear delineation between the two. They share common functionality via functions (like model and views), which is much easier to do when they're pure. You basically get the advantages of those magic frameworks without all the mag…

so your solution is a niche language nobody uses ?

Re: Better Auth – Authentication library for TypeScript

#24

Post by [deleted] »

aosaigh wrote: post #4

As someone developing with both Nuxt and Next, I find these "full-stack" JavaScript libraries and frameworks really confusing and difficult to grok. I understand the benefit of only having one ecosystem to worry about (JS/TS in Node and browser) but I'm not convinced that having backend and frontend in the same codebase is actually a good idea. It might be due to being a more "old school" full stack developer, but th…

[deleted]

Re: Better Auth – Authentication library for TypeScript

#26

Post by eezing »

Recursing wrote: post #12

Does anyone have experience with https://lucia-auth.com ? OP says that it's deprecated, but it seems like it just changed from a library to a short guide on how to implement auth yourself. I'm planning to migrate our authentication and session management from auth0 to this to save costs and make things simpler.

This is actually very nice, thanks for posting.

Not sure this will save you time and money, but it is very comprehensive.

Re: Better Auth – Authentication library for TypeScript

#27

Post by aosaigh »

Aeolun wrote: post #16
aosaigh wrote: post #4

As someone developing with both Nuxt and Next, I find these "full-stack" JavaScript libraries and frameworks really confusing and difficult to grok. I understand the benefit of only having one ecosystem to worry about (JS/TS in Node and browser) but I'm not convinced that having backend and frontend in the same codebase is actually a good idea. It might be due to being a more "old school" full stack developer, but th…

Ok, but how is that related to this auth library?

It’s a full-stack auth solution for full-stack JS frameworks

Re: Better Auth – Authentication library for TypeScript

#28

Post by oDot »

fsndz wrote: post #22
oDot wrote: post #14

Earlier quoted context omitted.

I am a big fan of Gleam language's Lustre[0], and due to its functional nature, the full stack experience is much better. Instead of becoming this mishmash of backend and frontend, there's a clear delineation between the two. They share common functionality via functions (like model and views), which is much easier to do when they're pure. You basically get the advantages of those magic frameworks without all the mag…

so your solution is a niche language nobody uses ?

Isn't that what every technology was at some point?

Re: Better Auth – Authentication library for TypeScript

#30

Post by tomas789 »

aswerty wrote: post #21
aosaigh wrote: post #4

As someone developing with both Nuxt and Next, I find these "full-stack" JavaScript libraries and frameworks really confusing and difficult to grok. I understand the benefit of only having one ecosystem to worry about (JS/TS in Node and browser) but I'm not convinced that having backend and frontend in the same codebase is actually a good idea. It might be due to being a more "old school" full stack developer, but th…

100% agree with how confusing it all feels. Smudging data and code back together feels like a massive step backwards. I can't but be reminded of the disaster that was ASP.NET Webforms. It took me a while to grok that in SSR frameworks, you shouldn't treat the SSR backend as a data backend. The best mental model is that the "SPA" just now has a client-server boundary in the middle of it. You should have a normal data…

In my, arguably limited experience compared to some other folks, completely agree. It feels lite the correct solution here is to treat it as another kind of backend. I always keep the truth-keeper backend separate and with much higher quality requirements.
Post reply on HN