Live data from Hacker News

Will PocketBase Survive?

github.com

11–13 of 13 posts

Re: Will PocketBase Survive?

#11
post #5

Earlier quoted context omitted.

Yep, but the situation hasn’t changed. In fact, ~~development velocity has slowed recently~~ PocketBase has been in a feature freeze recently. But like with any project like this, you need to weigh up the pros and cons of whatever tech stack you choose. PocketBase at least is MIT licensed, so you can fork and fix/add new features if you want. If you’re running a successful business with PocketBase as a backend, it mi…

Wasn't the feature freeze in preparation to v1? Not saying is hasn't slowed down, but it seems reasonable

Not sure he explicitly said that, but he’s said that there’s a bunch of technical debt he wants to fix through refactoring etc, which will be v0.23, I’m not sure path goes to V1 next (at least directly) but it may. He also stopped accepting donations in Jan saying that he felt like donations came with expectations. I’m not saying it’s not reasonable, just that the whole ethos behind PocketBase is “I’m building this, you folks are all welcome to use it, but I don’t owe you anything” (completely fairly).

Asking “will it survive” is the wrong question. It’s already there, works, and is used by thousands of people. Whether it gets updates or not depends entirely on whether Gani wants to and is able to keep updating it. No one can answer that except Gani, and he’s saying “no promises”.

Re: Will PocketBase Survive?

#12
post #3

I really like Pocketbase as a simpler and locally hosted Firebase/Supabase alternative (yes I know Supabase can be self-hosted but its pretty heavyweight) except for one major disadvantage - the lack of a NULL primitive type. There's no ability to set null as a value of an item despite null being a perfectly valid data type in SQLite (which is what Pocketbase uses). Having to arbitrarily assign a MAGIC CONSTANT value…

[dead]
Post reply on HN