• 3 Posts
  • 1.65K Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle

  • I don’t really know jack about supabase, but what I’m getting at is that authentication is tied to a user store somewhere. So your user authenticates, they do so against something. Either your server or your database. If they do it against your database, then fine, but how did that user get created? How are they making the connection? How are your policies applied for that user? What keeps a user from spamming your database with login attempts to guess other users or your root db user?

    If your users have to authenticate against a server you don’t have to worry about the database. You can use a authentication library for your language and you’re good to go in most cases. You can then also scale your database separately.

    Maybe supabase is designed for this, idk, but I personally wouldn’t ever design a site that way, unless it was a very very niche circumstance.






  • So you set up a nice strawman with assembly and fortran there (which would never be used for a web server) instead of suggesting a realistic option like C# or the JVM, both of which have much larger communities of people that actually know what they’re doing.

    You’d get just as many contributions in Java or Kotlin and the quality would be higher as well.

    The decisions at the start of the project have the most influence on the project, more so than anything ever will later down the line.













  • My wife and I complain about shows constantly (I’m talking about the shows and movies we like!), pausing to point out every little thing, and I’m in absolutely no way a movie critic, in fact I hate most shows that critics like. If I was to watch a show where I hated every character I would be pausing every five seconds (this isn’t hyperbole, I’m being serious it would be every five seconds) to complain more and more. The show isn’t enjoyable when there’s literally zero reason to like anyone in it.