The author seems like they really care and are competent.
They should go work for render.com
Heroku: We’ve Heard Your Feedback
121–130 of 151 posts
Re: Heroku: We’ve Heard Your Feedback
#122Earlier quoted context omitted.
There really aren't any Heroku leaders anymore. I think anyone director level or higher is Salesforce—not Heroku. It's worth mentioning that this isn't a result of Salesforce acquiring Heroku. That happened 12 years ago when Heroku was next to nothing. Salesforce gets credit for investing in and making Heroku. Why they ultimately have decided to give up on it I have no idea. I hear it's because salespeople had a hard…
Salesforce is where good software goes to die (or at best become stagnant and lame). Same thing happened to quip and will happen to slack.
Oh man, I somehow missed Slack had been acquired by Salesforce. So many things make sense now!
Re: Heroku: We’ve Heard Your Feedback
#123As a former herokai, communication was always the #1 point of discussion internally. This idea that they "can" do better is a half truth. They DID do better. I leave it as an exercise to the reader to determine what the limiting resource was here. By the way, how many senior devs and cofounders are left at Heroku Bob? Why doesn't it show up at dreamforce anymore?
(Former) Salesforce employee here, long enough to have been there a couple of years before the Heroku acquisition. I can't let this stand without a comment. Heroku never seemed to want to integrate, but instead be the "cool kids", those who just do not have to worry about the enterprisy stuff such as automated backups, DR, high availability, enabling Java, etc. Everything they did was great, everything "Salesforce" s…
> Heroku never seemed to want to integrate, but instead be the "cool kids", those who just do not have to worry about the enterprisy stuff such as automated backups, DR, high availability, enabling Java, etc.
Seems like Salesforce got exactly what they bought. Not sure why they’d be surprised about it.
Re: Heroku: We’ve Heard Your Feedback
#124Earlier quoted context omitted.
> 2. Customers sign up at "heroku.com", the platform is called "Heroku", the CLI is "heroku", everything's heroku, so don't send emails from a parent company (Salesforce), send them from "Heroku". They're working on something called "Project Periwinkle" that is intended to remove all Heroku branding and make everything Salesforce branded. Periwinkle being a colour between blue (salesforce) and purple (heroku). No mor…
Any suggestions on a rival PaaS that has a similar engineering philosophy to the old Heroku?
Cloud Foundry maybe? Some companies are offering it as a service (e.g: IBM Cloud Foundry)
Re: Heroku: We’ve Heard Your Feedback
#125> We’ve heard your feedback on our communications during this incident. You want more transparency, more in-depth information, and fewer “we are working on it” posts. Well, those, and : 1. Speed. It took days for heroku customers to be told about this. 2. Customers sign up at "heroku.com", the platform is called "Heroku", the CLI is "heroku", everything's heroku, so don't send emails from a parent company (Salesforce…
Considering how badly Salesforce handled communication and bug fixing of log4shell in Tableau that's not really surprising.
Re: Heroku: We’ve Heard Your Feedback
#126Curious why they would need to keep the GitHub integration down for a while longer. Are they afraid someone could still grab credentials?
GitHub is not allowing them to turn it back on yet (source: multiple people on both sides)
GitHub should insist on it being converted to a GitHub App before they allow it to be re-enabled.
That way org admins can see the requested permissions and control exactly which repos are permitted. GitHub OAuth apps are an absolute nightmare to audit or control.
Re: Heroku: We’ve Heard Your Feedback
#127Earlier quoted context omitted.
Salesforce is where good software goes to die (or at best become stagnant and lame). Same thing happened to quip and will happen to slack.
Oh no! I hope Slack doesn’t become slow and bloated, or go through unnecessary UX redesigns. /s
MS teams is proof slack could get a lot worse yet :-)
Re: Heroku: We’ve Heard Your Feedback
#128Earlier quoted context omitted.
Sorry but Render at their lunch entirely. Try it. https://render.com/docs/deploy-rails Want simple? Use a build.sh Want a bit complexity? Use a Dockerfile. Their docs are really copy paste for 99.9% applications. Whoever in that company made the decision to invest in docs was right on the money. It made switching to them a much easier choice. https://render.com
I'm moving a small amount of stuff ($250/mo spend) off Heroku this weekend. It's either Render or Fly, and I guess I'm going to start with Render. Here's where I'm starting: https://render.com/docs/migrate-from-heroku
Update: Migrating the simplest possible Rails app from free-tier to free-tier didn't work on Render (deploys fail, no logs to be found), so I'm bailing out to try Fly.
To any render people reading this, it appears to have been an issue with the migration plugin and the Heroku-18 stack. Manually deploying the app worked fine.
Re: Heroku: We’ve Heard Your Feedback
#129> We’ve heard your feedback on our communications during this incident. You want more transparency, more in-depth information, and fewer “we are working on it” posts. Well, those, and : 1. Speed. It took days for heroku customers to be told about this. 2. Customers sign up at "heroku.com", the platform is called "Heroku", the CLI is "heroku", everything's heroku, so don't send emails from a parent company (Salesforce…
> 2. Customers sign up at "heroku.com", the platform is called "Heroku", the CLI is "heroku", everything's heroku, so don't send emails from a parent company (Salesforce), send them from "Heroku". They're working on something called "Project Periwinkle" that is intended to remove all Heroku branding and make everything Salesforce branded. Periwinkle being a colour between blue (salesforce) and purple (heroku). No mor…
> New features have been banned for years. Only "keep the lights on" projects are allowed.
That's what it's looked like from the outside -- that no features were for whatever reason(s) no longer going to happen. But still dismaying to hear it from the inside in those terms.
Re: Heroku: We’ve Heard Your Feedback
#130Earlier quoted context omitted.
I'm moving a small amount of stuff ($250/mo spend) off Heroku this weekend. It's either Render or Fly, and I guess I'm going to start with Render. Here's where I'm starting: https://render.com/docs/migrate-from-heroku
Update: Migrating the simplest possible Rails app from free-tier to free-tier didn't work on Render (deploys fail, no logs to be found), so I'm bailing out to try Fly. To any render people reading this, it appears to have been an issue with the migration plugin and the Heroku-18 stack. Manually deploying the app worked fine.
Update for fairness: Fly.io failed even quicker.
Creating postgres cluster redacted-db in organization redacted Launching...⣻ Error failed creating the Postgres cluster redacted-db: Timeout on CreatePostgresCluster.app
Every attempt fails. There's no way I can run this for $250/mo on AWS. Now I have to pretend I'm a sysadmin and use Hetzner.