Last time a post about Heroku was posted, I talked about my great experience using Coolify:

I am using Coolify (https://coolify.io), an open source self-hosted PaaS which is a relatively newer kid on the block compared to Dokku and CapRover. I tried both of these and I just didn't like how they were, always had some problem or another.

In contrast, Coolify has a great GUI that abstracts away the most common things about PaaS hosting, like connecting to GitHub automatically for git push deploys, SSL certificates, reverse proxying and custom domain support, and best of all, having support for Heroku style buildpacks as well as Dockerfiles. I've been quite happy with it, the creator has a Discord and responds to issues very quickly.

With regards to non-self-hosted options, I did try out Render, Fly.io and Railway but I found that their free servers were too anemic. I was compiling a Rust backend and it simply could not compile on their free servers. On Hetzner, for 5 bucks I could get a 2 AMD vCPU and 2 GB RAM machine that was sufficient to compile my Rust apps in a way that the non-self-hosted ones were not. I have a JS frontend app that works fine though but I wanted to keep everything under the same VPS, plus I can run other types of self-hosted services on it too, like Plausible analytics and a Ghost blog. I'm not sure if those are allowed on non-self-hosted options.

All in all, it costs me 5 bucks a month, and I never have to worry about sudden upcharges for traffic à la AWS as in the very worst, my VPS goes down for a while. I'm now running about 20 different services on this 5 dollar box including databases and applications as well as other services, works just fine.

My brain immediately jumped to "but you can just git reflog and then copy the state you want to revert to and then git reset --hard <commit>", but not only is that not simple or obvious, it isn't even correct, since a commit or amend operation can be performed with only some of the changes staged, and a hard reset will wipe out anything unstaged. Ah sigh.

So yes, in short I agree.

I have only dabbled in Rust and have no experience with C++/Java/Go. Can you help me understand how those languages would be more memory safe than Rust? My understanding was that safe code was a solution to memory leaks. What’s the benefit to safe rust code if it isn’t getting rid of memory leaks?

This topic came up a few weeks ago and I commented [0] that I started using Coolify (https://coolify.io), an open source self-hosted PaaS that's similar to CapRover and Dokku but in my opinion the developer experience is a lot simpler since it has a GUI unlike Dokku (non-Pro version, anyway) and the deployment was easier than CapRover since it connects directly to your GitHub/GitLab account via their API.

I've used a lot of the alternatives listed here but each one had some drawback or another. In contrast, I got a cheap 5 dollar Hetzner server and it's more powerful than any of what the free options here give you (Hetzner gets you 2 AMD vCPUs and 2 GB RAM), plus unlike AWS I never have to worry about whether I'm gonna randomly pay $10k this month due to a traffic spike. The only thing that was missing before was a good PaaS solution for the server (and I used to use Dokku before primarily) but Coolify solves that neatly.

[0] https://news.ycombinator.com/item?id=33077118#33077464

This sucks and it’s the same as EasyMotion from 10 years ago.

Vim is imperative editing. You have to tell the computer how to edit by glueing together small nasty commands. It gives you “Vim problems.” The mouse is arguably a declarative solution. “I declare I want to edit here.” So much nicer and more efficient.

That's what 'n' is for. It also doesn't overwrite the 's' keybinding which is already used for substitution. I don't see the point of this plugin for people who are actually familiar with vim's keybindings.

you know simple / works just fine for me :P