3 ms·
My biggest complaint is that your copy (here, and on the site) uses delusional and grandiose language. Which shows me that you're just full of it. And surprise:
by usernamed7 3y ago
My biggest complaint is that your copy (here, and on the site) uses delusional and grandiose language. Which shows me that you're just full of it. And surprise: people don't buy from people they don't trust.
and then there's this BS from the site:
>Its core, written in pure Golang, is of exceptional quality. Golang is esteemed for its productivity, simplicity, safety, and portability. With Pocketbase, your app—including public files—can be compiled into a single static binary deployable on any server, epitomizing true vendor independence.
The only thing this epitomizes is a solution in search of a problem.
Also from the site:
> Frameworks like Django and Rails offer pre-packaged solutions for common issues such as user authentication and template rendering, liberating developers to concentrate on solving business problems. They’re great for indie developers and integrate well with HTMX. However, there’s a caveat: over time, your expertise may become confined to the Python or Rails ecosystems.
What is this dribble? So the large and well documented python/rails ecosystems are bad, but using a boilerplate written by some guy is somehow better?
It's cool that you built something.
It's absurd that you're trying to sell it to developers as "the SaaS boilerplate for engineers".
It is clear you do not understand the audience you are trying to sell into. You don't understand their pain, and you don't understand how they make decisions.
- mannders 3y agoSimply put, I found deploying a Django app on an EC2 instance to be a huge pain. Getting letsencrypt certs through nginx, setting up routes to a unix socket, choosing between WSGI and ASGI. Docker compose can help orchestrate these processes more easily, but its still a non-trivial amount of complexity. This isn't a documentation problem, but a personal distaste for the architecture. This is the problem your first quote actually solves. I didn't fabricate a fake problem, I felt a real one. Deploying a pocketbase application is as simple as getting a binary on a server with a HTTPS configured firewall, and giving it a domain name. I launched both deploysolo.com and deploysolodemo.com in a tmux instance, which isn't a great permanent solution, but a testament to ease of deployment for a market validation phase. The "for engineers" generally comes from the fact that many web software engineers enjoy the Go ecosystem, and they can take a lot of their expertise creating HTTP routes into a SaaS boilerplate that solves common problems out of the box. Reinventing the wheel sucks when you have a business idea to get out into the world. Anyway truly thank you for the feedback, I'm still learning and not trying to use grandiose language to extract money. I'm just trying my best to create something that helps people create their own value.