[meter]

> the way Heroku worked…

The author implies that something has changed — and that nowadays, you can’t `git push heroku main`. But according to the docs, it’s still just as simple.

I guess I don’t understand how Heroku’s DevEx has changed. Seems just as intuitive as it’s always been. But I could be missing something.

[cjk]

What I took away from the post is not that Heroku no longer works like that, but that it's a sinking ship, and thus not advisable to use any longer.

[ryantgtg]

I struggled to follow parts of this article. She discussed taking to the CTO about bad insurance, and then followed that section with “I got hired.” The whole thing meanders and barely has a point or provides evidence, and I’m not truly convinced it’s a singing ship. That said, I do defer to ex-employees on this matter.

I’m mostly looking for alternatives because people keep saying I should (and I could possibly get double the ram for the same price). But I just git push heroku mastered 5 minutes ago and it took about 1 minute to build, and it was wonderful.

[xena]

I was a contractor before I was an employee because Salesforce was starving the beast until they made CRM features. Never work with MBO Partners. They do not give two shits about you, just your money that they take a huge percentage of.

[ryantgtg]

Thanks.

Not too long ago I was like “we’ve been paying heroku $59/mo for years (open source, non-commercial, funded by patreon) and while I don’t have any issues I can’t tell if it’s kind of in maintenance mode or what.” So I checked the blog and saw posts like “Faster Dynos for All” and their email newsletter which regularly mentions improvements to service. From those I felt reassured that they’re still improving it. But then came a wave of “heroku alternatives” and posts lamenting how heroku is blowing it. I’m grateful to hear reports from the other side (though again, my personal experience with heroku is still totally fine - and we don’t do the github integration)!

[oxff]

Based on Salesforce's handling of the April / May security breach / incident I would not recommend Heroku, not even to other developers who understand risks and would just use it for hobby / throwaway projects.

Gonna have to test all the meme alternatives soon, fly / render / glitch / porter.

[wutwutwutwut]

So like talking about your 97-year-old grandmother in past tense, as if she was already dead, because she will be in a year or two.

[tinco]

I wouldn't bet my income on my 97-year-old grandmother for surviving as long as I promised my clients their website would stay online.

That said, I don't think Heroku is that close to being sunset, but that's my guess, and that guess is as good as the people who say it is. I'm currently messing around with fly.io and that product is so young one would be crazy to think it has better chances to last the next decade than Heroku does.

[jrochkind1]

I don't think Salesforce is probably planning on sunseting Heroku anytime soon.

But they seem to be totally starving it, allocating it the minimum of resources they think they can to keep it going pretty much as it is without any new features.

Based on how they handled the recent security update, I won't be surprised if it... just kind of crumbles into the sea at some point.

We all know that software doesn't just "keep working" at all without continual maintenance. For several different reasons, security being one of them. Heroku's ability to keep "just working" with the languages/platforms it does, as new versions of such come out, seems to be dependent on an increasingly smaller workforce that goes above and beyond.

[nomilk]

The word "worked" could just as well be "works" (present tense) because Heroku still works exactly as the author describes (I think the author is recounting how it worked when they were there, hence why they use past tense).

[bin_bash]

There was discussion about this the other day:

https://news.ycombinator.com/item?id=31313779

[geoffharcourt]

`git push heroku main` doesn't work if your repository is large enough (not sure if this is raw file sizes or the Git data size). Some of our apps can't be redeployed using this method, we have to use the build workaround which has its own set of issues.