3 ms·
The problem isn’t that you’re charging too much, or that there’s anything wrong with Deployments per se. The problem is the rate of change. If I have to keep up
by ksenzee 3y ago
The problem isn’t that you’re charging too much, or that there’s anything wrong with Deployments per se. The problem is the rate of change. If I have to keep up with a product that’s changing this often, I might as well self-host.
- KomoD 3y ago> I might as well self-host. Then do that, nobody is stopping you.
- ksenzee 3y agoMy point is not “wah wah I have to self-host.” I maintain a CMS backend for a living. I know how to host a website. I’m just saying that this transition has been made particularly annoying for the hobbyists being left behind, because it’s costing not only money but also time. There’s no “just let me pay for the existing service” option. It’s like an acqui-hire where they shut the service down instead of just keeping it running and taking people’s money.
- sorenrood 3y agoIt might not be clear from this post, but nothing is changing (w/ deployments/always on/repl.co hosting) until January 1st, 2024.
- ksenzee 3y agoRight, I did see that. I get to pick any evening I want during the next ten weeks to do my futzing with the thing I was hoping to pay to leave alone in perpetuity.