Heroku was one of the first to have that seamless UX, only after which others like Fly or Render or Railway came to copy it. I wager people were primarily attracted to that user experience and only minimally cared that it was fully hosted versus not, because there was also AWS at that time.
replyHow do you think self-hosting affects that seamless UX they value.
replyAs I said, the correct software on top handles it all for you. I don't think you've actually tried Dokploy.
replyDokku is better. And neither is what Heroku's bread and butter customer needs.
replyBut alas, my interest in painstaking explaining why self-hosting is fundamentally incompatible with a product who's value prop was "nothing to install" is waning.
Have a good one.
You and I simply have different opinions on what Heroku's value proposition was, because, again, AWS was also right there and also was "nothing to install." Therefore Heroku was used primarily for its dead simple UX, something which is replicated even in a self-hosted environment, because, again, the value prop was never about PaaS or self-hosting, it was always about the user experience.
replyHave a good weekend.