Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Heroku: We’ve Heard Your Feedback

blog.heroku.com

Post reply on HN
Print view View original

61–70 of 151 posts

Re: Heroku: We’ve Heard Your Feedback

#61

Post by derefr »

throwawa3238273 wrote: post #46
nomilk wrote: post #18

> 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…

Any suggestions on a rival PaaS that has a similar engineering philosophy to the old Heroku?

Re: Heroku: We’ve Heard Your Feedback

#62

Post by ricardou »

alasdair_ wrote: post #57
RileyJames wrote: post #19

“I have a lifelong enthusiasm for developers and the experience they have building software together” And then drops a link to contact them, via LinkedIn… LinkedIn is the polar opposite of GitHub. It’s the worst example of social media, from its news feed, to spam invites. And it’s broken every rule in the “be a good netizen” play book, from constant spam, to slurping your email contacts and surveillance to the extre…

I assume it’s so that they can mine your LinkenIn connection data and make it available to their sales teams to upsell you and people you know. I’d imagine they would end up storing all that data in some kind of web-based CRM, possibly sold as a SAAS product.

Hmm, yeah, maybe one where with "sales" in its name. I think you're into something here.

Re: Heroku: We’ve Heard Your Feedback

#63

Post by 1propionyl »

derefr wrote: post #61
throwawa3238273 wrote: post #46

Earlier 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?

If you want a more minimal do-it-yourself option you could self-host something like Dokku[1].

[1] https://dokku.com/

Re: Heroku: We’ve Heard Your Feedback

#64

Post by orangepurple »

Sebb767 wrote: post #26
bpeebles wrote: post #13

Earlier quoted context omitted.

There doesn't seem to be anything different now than 6 hours ago. So posting it after 8pm EDT/5pm PDT Friday seems very intentional.

With what intention? Honest question, I don't see a strategic advantage in posting this on a Friday. More of a disadvantage, actually, with less visibility.

With any hope it will slide in the news cycle and be buried by any developments over the weekend.

Re: Heroku: We’ve Heard Your Feedback

#65

Post by spacemaiv »

sergiotapia wrote: post #35
nakovet wrote: post #22

Heroku is a one of kind platform, many tried to replicate, none have come close, the ability to setup a whole app with a few clicks on dynos and add-ons is great. The price was always salty $50/month for 1gb RAM shared CPU, and in the few past years no newly released features comes to mind. As a customer I have no idea what this security issue impact, the communication has been poor as this post does not clarify much…

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 hadn't heard of Render prior to this incident, but now I see it recommended in almost every related thread. Of course, Heroku's free tier had always worked well enough for my hobby apps, so I had no reason to search for alternatives. Looking forward to giving Render a try.

Re: Heroku: We’ve Heard Your Feedback

#66

Post by throwawa3238273 »

neximo64 wrote: post #55
throwawa3238273 wrote: post #46

Earlier 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…

The amount of Salesforce fluff in the post is quite palpable. There is a clear lack of control with the leaders in Heroku judging off this post because of the salesforce transition. This project Periwinkle sounds awful. Basically thats the end of using Heroku for us. If it remains like this its something to judge from.

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 time understanding how to sell it which seems like a strange reason to give up entirely.

Re: Heroku: We’ve Heard Your Feedback

#67

Post by ezekg »

> Additionally, we have no evidence that the attacker has accessed any customer accounts or decrypted customers’ environment variables.

Now the attackers had access to encrypted environment variables?

Re: Heroku: We’ve Heard Your Feedback

#68

Post by pdwittig »

derefr wrote: post #61
throwawa3238273 wrote: post #46

Earlier 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?

I was a long time Heroku user/lover (~10 years) for both personal and company projects. I've recently moved to Render[1], and so far it's been great. I haven't been using them long enough to put it through it's paces, but I'd certainly say it's worth a look. Other alternatives I've heard good things about are Fly.io[2] and Porter[3].

[1] - https://render.com/

[2] - https://fly.io/

[3] - https://porter.run/

Re: Heroku: We’ve Heard Your Feedback

#69

Post by ryantgtg »

zebraflask wrote: post #59
nomilk wrote: post #18

> 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…

This all somehow seems unsurprising. If anyone has tried to use Heroku in easily the last year, the number of times you get failed builds over really trivial things is noticeable.

I haven’t experienced a failed build in a few years.

I did try a heroku competitor recently and my builds failed. And there was no detailed log to show why. So I couldn’t troubleshoot it and I immediately gave up!

As an aside, I was really hoping this post was going to be “we read that one competitor’s blog post last week clearly detailing all the areas where we can improve, and we HEAR you.”

Re: Heroku: We’ve Heard Your Feedback

#70

Post by psaux »

Let’s give Bob a chance. I worked with him at AWS and prior. He is very committed to the customer, hence his post. We all try to communicate the best we can, so please try to support him in his new role.

I launched several startups on Heroku over the last decade +, and feel they have gravity on trust. Some of the best devs I have worked with.

Post reply on HN