←back to thread

Poor Man's Back End-as-a-Service (BaaS), Similar to Firebase/Supabase/Pocketbase

(github.com)
200 points dcu | 1 comments | 03 Jul 25 15:35 UTC | HN request time: 0.204s | source
Show context
miroljub ◴[03 Jul 25 16:04 UTC] No.44456449[source]▶
I don't understand why create a new project instead of contributing to Pocketbase, which looks very similar. What does it bring that is not already there in Pocketbase?
replies(5): >>44456659 #>>44457149 #>>44457242 #>>44457311 #>>44459178 #
1. Imustaskforhelp ◴[03 Jul 25 17:09 UTC] No.44457149[source]▶
I always used to feel this about why? But I mean, I've always felt like its the author's choice as to why they are doing this. And we think of it as a binary option (That they want to contribute to some other project or this) but I feel as if we don't think that maybe we had a binary option of this or absolutely nothing.

Now what I do like though is the second line of your post. What are the comparisons... Now IMO, the biggest thing is that this thing is genuinely really tiny (less than 1k loc is wild) and maybe they really followed the occam's razor and just ditched sql and the simplest sql (sqllite) altogether for the sweet csv.

I never thought there would be a day where I would have to say that sqlite would be the one complex given how in all senses sqlite is like the most simplest / embeddable sql database or databases in general. Maybe I am going into a tangent but I love sqlite and what pocketbase does tbh. I think of sqlite + per user db and I just get so happy thinking about this architecture tbh. I love sqlite.