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 might be sensible to do this anyway, and potentially hire a Go dev or consultant to do whatever work you need doing, rather than hoping Gani has it on his priority list.
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”.
Not sure he wants it. PocketBase is just a backend he developed for his main project, Presentator, and everything I’ve read from his conversations are “Yep, I’m publishing this because someone else might get some use out of it but I’m not developing by consensus here”, and I don’t think he wants it to be his full time job (he’s always super polite and helpful, not trying to imply he’s rude or dismissive or anything).
Obviously everyone has a price, so maybe I’m wrong, but even then you’ve not solved the “bus factor” problem.
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 might be sensible to do this anyway, and potentially hire a Go dev or consultant to do whatever work you need doing, rather than hoping Gani has it on his priority list.