Live data from Hacker News

Ask HN: Are you leaving Heroku?

news.ycombinator.com

81–90 of 114 posts

Re: Ask HN: Are you leaving Heroku?

#81
post #75
post #65

Earlier quoted context omitted.

Fly.io doesn't track Heroku buildpacks nor does it recommend buildpacks as a first class workflow. Buildpacks are very underdocumented. The official tutorial and guides pushes Docker as the "preferred" workflow. Docker is nice for environments like Rust/Go/when you have additional dependencies. For Ruby/Python/Node buildpacks are a lot easier. Your typical Heroku tutorial says "use cedar-XYZ pack for Python Z and eve…

I mean, you're mostly right. Not about the "hiding behind blog posts" thing (we just like to write). But the rest of it, sure? We're not telling you to stop using Heroku. We love Heroku. Heroku is a big part of why we got into this. Our primary benefit over Heroku isn't "the simplest possible DX". Heroku has that nailed! It's running apps close to users, easily scaling them up and out over the globe. I like us a lot…

I want to use Fly, not Heroku. But Fly just doesn't seem to live up to my expectations right now :(

I understand that you believe your competitive advantages stem from the edge server deployments. Sure that may be true for certain serverless and HTML-over-the-wire workloads like Phoenix, but if you actually talk to your customers, a significant number of us want a Heroku replacement, not just fancy docker-at-edge.

Re: Ask HN: Are you leaving Heroku?

#82
post #2

You might also note there has been little to no feature development for Heroku in some time

Not just that, trivial bugs aren't getting fixed. The charts showing response times, for instance, sometimes go crazy when you change the settings for time window or interval.

Any other seemingly trivial bugs that are frustrating you? Would love to get your list.

Re: Ask HN: Are you leaving Heroku?

#83
post #81
post #75

Earlier quoted context omitted.

I mean, you're mostly right. Not about the "hiding behind blog posts" thing (we just like to write). But the rest of it, sure? We're not telling you to stop using Heroku. We love Heroku. Heroku is a big part of why we got into this. Our primary benefit over Heroku isn't "the simplest possible DX". Heroku has that nailed! It's running apps close to users, easily scaling them up and out over the globe. I like us a lot…

I want to use Fly, not Heroku. But Fly just doesn't seem to live up to my expectations right now :( I understand that you believe your competitive advantages stem from the edge server deployments. Sure that may be true for certain serverless and HTML-over-the-wire workloads like Phoenix, but if you actually talk to your customers, a significant number of us want a Heroku replacement, not just fancy docker-at-edge.

It seems reasonable that we wouldn't be living up to your expectations; there's no single best place to host things, and Heroku is a great platform. We're Fly.io, not Fleroku.

Re: Ask HN: Are you leaving Heroku?

#84

All these "big clouds" are a risk when it comes to global outages. Heroku, Cloudflare, AWS... etc. Using indy or smaller developer focussed clouds can mitigate this problem, but those come with other risks for sure. I think every tech decision makers (CTOs, architects, lead engineers...) need to know at least some of these tools and give them a try to keep a list of plan-Bs at hand.

What leads you to believe indy or smaller clouds are less prone to outages?

Re: Ask HN: Are you leaving Heroku?

#85

Earlier quoted context omitted.

Not just that, trivial bugs aren't getting fixed. The charts showing response times, for instance, sometimes go crazy when you change the settings for time window or interval.

Any other seemingly trivial bugs that are frustrating you? Would love to get your list.

Forget little bugs... the big picture is far more important. I cannot recommend anyone use this product given recent (years) inattention.

Since you work for Heroku / Salesforce, letting your users know if this is a dead product or not would be a good first step. If not dead, explain why there have been no updates and what is to be expected moving forward.

Re: Ask HN: Are you leaving Heroku?

#86

Earlier quoted context omitted.

Any other seemingly trivial bugs that are frustrating you? Would love to get your list.

Forget little bugs... the big picture is far more important. I cannot recommend anyone use this product given recent (years) inattention. Since you work for Heroku / Salesforce, letting your users know if this is a dead product or not would be a good first step. If not dead, explain why there have been no updates and what is to be expected moving forward.

Heroku is very much alive. On your comment about what is to be expected.... stay tuned.

Given that, I also don't want to forget the little bugs, I believe they are important to a great user experience. I think this is true for any product, but especially true for Heroku.

Re: Ask HN: Are you leaving Heroku?

#87
Reposting this because fuck Heroku:

A former employer was mad at me for daring to leave my job and made a malicious DMCA claim against my website. Heroku took it down with zero notice and treated me like a criminal when I called them to quit their bullshit.

They said I was not allowed to ever host the falsely claimed content on Heroku ever again. They said that I should pursue external avenues for disputing the claim. I took my site off Heroku and kept it offline because of the implicit threats of lawsuits from my previous employer. The site was my online portfolio of work and experience I was using for job hunting. However, my Heroku account was also used to host my profit-generating website/business, and instead of taking down only my portfolio site, they took down every site on my account. My account was completely disabled and I wasn't able to even remove the specific site and put my other ones back online, which is why I had to call them to re-enable it, but only after they treated me like shit and like I was murdering babies even though I told them the DMCA claim was malicious.

Re: Ask HN: Are you leaving Heroku?

#88
post #73

Earlier quoted context omitted.

I can only speak about render.com which I've seen recommended several times. I was thoroughly unimpressed. Heroku is my go to when I want to spend no more than 5 minutes getting a microservice deployed. Otherwise I would use DO. Render seemed to be the longer and clunkier experience of DO without the benefits of DO.

(Render founder) Any chance we could connect about the issues you saw with Render? Email in profile. Lots of former Heroku customers spending thousands of dollars every month have successfully made the switch to Render and are quite happy (as you can see elsewhere on HN). I'd appreciate a chance to address your pain points with us.

Probably not, but generation focus is pretty good at connecting companies with specific subsets of users. I know they already maintain a list of current heroku devs.

Re: Ask HN: Are you leaving Heroku?

#89
post #75
post #65

Earlier quoted context omitted.

Fly.io doesn't track Heroku buildpacks nor does it recommend buildpacks as a first class workflow. Buildpacks are very underdocumented. The official tutorial and guides pushes Docker as the "preferred" workflow. Docker is nice for environments like Rust/Go/when you have additional dependencies. For Ruby/Python/Node buildpacks are a lot easier. Your typical Heroku tutorial says "use cedar-XYZ pack for Python Z and eve…

I mean, you're mostly right. Not about the "hiding behind blog posts" thing (we just like to write). But the rest of it, sure? We're not telling you to stop using Heroku. We love Heroku. Heroku is a big part of why we got into this. Our primary benefit over Heroku isn't "the simplest possible DX". Heroku has that nailed! It's running apps close to users, easily scaling them up and out over the globe. I like us a lot…

I like this reply. Not a user of either system currently, but have done projects on both. The use-case for fly.io is strong, but everyone needs to focus on where they want to spend their time vs pay off.

Re: Ask HN: Are you leaving Heroku?

#90
post #18
post #13

Earlier quoted context omitted.

My main issue is the free redis and cheap postgres instances they provide for my low-traffic app.

You can get built databases deployed with Appliku as well. No reason to go broke on a small side project

on the same server? Heroku basically gives you 2 free vCPUs to run redis and postgres. If you run pg or redis on the same instance as the app server, then you're still down 2 vCPUs.
Post reply on HN