Live data from Hacker News

Heroku: We’ve Heard Your Feedback

blog.heroku.com

41–50 of 151 posts

Re: Heroku: We’ve Heard Your Feedback

#41

If you're on Heroku how do you deploy now? It says it's still weeks away before you can deploy - did I read this right?

You can deploy, you just can't trigger the builds automatically by pushing to Github. (This also means the Review Apps system is non-functional.)

Re: Heroku: We’ve Heard Your Feedback

#42
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

> Whoever in that company made the decision to invest in docs was right on the money.

Also the reason Django has always been so approachable (particularly in the early days, as it is orders of magnitude more complex now) and therefore popular

Older still, IMHO also why mIRC scripting was so much fun despite its shortcomings. The help file had literally everything you could want to learn about the language and it almost begged to be read. It's how I got into coding

Re: Heroku: We’ve Heard Your Feedback

#43
post #31

Earlier quoted context omitted.

re: 2 interestingly, when i log in or reauthenticate, or log in through the heroku cli, I get sent to https://verify.salesforce.com/v1/verify/

When I saw the Salesforce email I thought I was being spammed or phished or getting a job offer.

Those are all the same thing

Re: Heroku: We’ve Heard Your Feedback

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

When I got an email from Salesforce talking about Heroku I assumed phishing. Huge +1 on that 2nd point :)

Re: Heroku: We’ve Heard Your Feedback

#45
post #36

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

Email address is good but also an issue tracker or better yet IRC or something public would be good.

Agreed, for the specific issue. But it seems like he’s asking ppl to contact him more generally.

It does pose the question, what is the most developer friendly contact method??

GET /contacts

POST /message

Interested to hear ideas.

Re: Heroku: We’ve Heard Your Feedback

#46
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 more Heroku signups, you'll need a Salesforce account to use it. No more free tier either.

Heroku has been in the process of being sunset for years now. New features have been banned for years. Only "keep the lights on" projects are allowed. Not that they could do anything with the skeleton crew they have running the platform.

Bob Wise's LinkedIn doesn't even mention Heroku, only Salesforce. Lenora mentions the project here: https://www.lenoraporter.com/portfolio/salesforce

Source: I'm a former employee that left in protest because of this project.

Re: Heroku: We’ve Heard Your Feedback

#47

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

Former Heroku employee here: everything you list happened within the first year of acquisition.

You’re correct that the lack of real integration with SFDC was a large part of the problem though. Though as far as SFDC acquisitions go Heroku was cheap. More expensive ones had far worse outcomes even with integration.

Re: Heroku: We’ve Heard Your Feedback

#48
post #36

Earlier quoted context omitted.

Email address is good but also an issue tracker or better yet IRC or something public would be good.

Agreed, for the specific issue. But it seems like he’s asking ppl to contact him more generally. It does pose the question, what is the most developer friendly contact method?? GET /contacts POST /message Interested to hear ideas.

I guess it depends on what "developer friendly" means. If it means 'easiest method for a developer to contact me' that's email. It's ubiquitous. Everyone has at least one. It's easy.

If it means 'easiest method for only developers to contact me' that would probably be some documented REST API.

Either way, I agree the answer isn't Linkedin.

Re: Heroku: We’ve Heard Your Feedback

#49

“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 agree with you about LinkedIn. I also would have agreed with you about how silly that is, until I started working with giant banks and other huge finance industry people. Many of the devs there legit do use LinkedIn. A number of people actually blog and post updates and stuff on LinkedIn. It was really surprising. Startup culture and big corporate tech, despite using many of the same technologies, are miles apart culturally.

Re: Heroku: We’ve Heard Your Feedback

#50

If you're on Heroku how do you deploy now? It says it's still weeks away before you can deploy - did I read this right?

Deploy using heroku CLI: https://devcenter.heroku.com/articles/git#deploy-your-code

Unfortunately, git lfs isn't supported for CLI pushes, haven't found a way that works yet.

Post reply on HN