161–170 of 211 posts
Apparently 1 file just means a static go binary with a bunch of separate assets compiled in. I guess for some reason I was hoping for source code that was only one file.
Same here. At first, I thought it was a one-file-based database, which would have been even more commendable.
Earlier quoted context omitted.
Postbase, in contrast to PocketBase, doesn’t seem ready for primetime : ” Brand new project launched 02 Nov 2025, this is boiler plate but working! Expect heavy changes coming every few hours until stable Mostly all code is ChatGPT generated but manually tested by human.”
And by that description, I assume it's never going to be ready for primetime.
Now I'm glad I didn't find out pkcketbase earlier otherwise I'd never have made Postbase.
Regarding if it will ever be ready for prime time, time will tell.
The "SQLite doesn't scale" argument is usually just premature optimization masquerading as architectural wisdom. Unless you are actively hitting WAL contention limits (which is surprisingly hard to do on modern NVMe), the operational simplicity of a single binary beats the "scalability" of a distributed mess any day. We’ve normalized a complexity tax where every side project "needs" a dedicated DB cluster and a Redis…
The "SQLite doesn't scale" argument is usually just premature optimization masquerading as architectural wisdom. Unless you are actively hitting WAL contention limits (which is surprisingly hard to do on modern NVMe), the operational simplicity of a single binary beats the "scalability" of a distributed mess any day. We’ve normalized a complexity tax where every side project "needs" a dedicated DB cluster and a Redis…
I have a personal blog set up on the cheapest digital ocean droplet and i went ahead with sqlite for it, there is not much traffic on it and i think something like sqlite is actually the best choice for such projects. I did some benchmarking with a rust cli tool, the name i don't recall right now, something like apache bench but simpler. I wouldn't have the same performance if i had mysql or postgres running on the s…
The "SQLite doesn't scale" argument is usually just premature optimization masquerading as architectural wisdom. Unless you are actively hitting WAL contention limits (which is surprisingly hard to do on modern NVMe), the operational simplicity of a single binary beats the "scalability" of a distributed mess any day. We’ve normalized a complexity tax where every side project "needs" a dedicated DB cluster and a Redis…
The "SQLite doesn't scale" argument is usually just premature optimization masquerading as architectural wisdom. Unless you are actively hitting WAL contention limits (which is surprisingly hard to do on modern NVMe), the operational simplicity of a single binary beats the "scalability" of a distributed mess any day. We’ve normalized a complexity tax where every side project "needs" a dedicated DB cluster and a Redis…
Personally the lack of a decimal type make SQLite a no-go for me. Its too much of a hassle to do financial operations completely on the application side.
The "SQLite doesn't scale" argument is usually just premature optimization masquerading as architectural wisdom. Unless you are actively hitting WAL contention limits (which is surprisingly hard to do on modern NVMe), the operational simplicity of a single binary beats the "scalability" of a distributed mess any day. We’ve normalized a complexity tax where every side project "needs" a dedicated DB cluster and a Redis…
Personally the lack of a decimal type make SQLite a no-go for me. Its too much of a hassle to do financial operations completely on the application side.
Then just convert to dollars with a decimal place when needing to display, etc.
I recall this being pretty normal regardless of what database you use.
https://pocketbase.io/docs/going-to-production/#enable-setti...
https://github.com/pocketbase/pocketbase/blob/90d896e1cc49e3...
The developer doesn't consider this a security issue. I hope they reconsider. Non-standard cryptography is a minefield.
Earlier quoted context omitted.
> nothing a skilled dev can't work around. Agreed. Loved this FAQ notice: "If you don't have the time to at least skim through the documentation and you plan to solely rely on some AI tool, then please do NOT use PocketBase!"
[flagged]