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

101–110 of 151 posts

Re: Heroku: We’ve Heard Your Feedback

#101

Post by [deleted] »

throwawaysfdc wrote: post #90
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…

Periwinkle never materialized. Neither did Shinrai, or a number of other projects that people brought up in hn threads about this incident. It’s clear that Heroku has lost a ton of great talent and momentum due to questionable business decisions but some of the most controversial fail to ever make it past codename status.

[deleted]

Re: Heroku: We’ve Heard Your Feedback

#102

Post by gonehome »

throwawa3238273 wrote: post #66
neximo64 wrote: post #55

Earlier quoted context omitted.

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…

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.

Re: Heroku: We’ve Heard Your Feedback

#104

Post by labster »

gonehome wrote: post #102
throwawa3238273 wrote: post #66

Earlier 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 no! I hope Slack doesn’t become slow and bloated, or go through unnecessary UX redesigns. /s

Re: Heroku: We’ve Heard Your Feedback

#105

Post by inopinatus »

hthrowaway wrote: post #15

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?

Is Matz still there?

Re: Heroku: We’ve Heard Your Feedback

#106

Post by hthrowaway3 »

throwawaysfdc wrote: post #90
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…

Periwinkle never materialized. Neither did Shinrai, or a number of other projects that people brought up in hn threads about this incident. It’s clear that Heroku has lost a ton of great talent and momentum due to questionable business decisions but some of the most controversial fail to ever make it past codename status.

It's on ice. As you say it's also not the first time they've attempted something like this.

Eventually they'll get there, but customers should know that's the direction. They'll be users of "Compute Cloud" writing APEX instead of Procfiles someday.

Re: Heroku: We’ve Heard Your Feedback

#107

Post by SonOfLilit »

pdwittig wrote: post #68
derefr wrote: post #61

Earlier quoted context omitted.

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/

Checked out render.com in the context of side projects that I want on the air but don't expect anyone to ever use (I have so many on heroku, who got rewarded for their generosity with many thousands of dollars of business from me), which means I'm willing to pay a few dollars but not to pay per-app. Looks great except that they delete your free databases after 90 days, making it completely useless for this use case. Their announcement blog post says they plan to remove this limitation "early 2022", but it hadn't happened yet.

I next looked at fly.io, which seem ok for the first two apps, assuming they use the same database. If I ever want more than two apps, it seems I will need to start hosting different apps together, which is the opposite of the headache-free experience I'm looking for.

Porter runs on my own cloud account, so I can't trust it to not cost too much.

Maybe I can get a Kubernetes cluster somewhere (DigitalOcean?) and deploy all my small apps to it, but it sounds like a headache.

I'm staying with heroku.

Re: Heroku: We’ve Heard Your Feedback

#109

Post by glenngillen »

inopinatus wrote: post #105
hthrowaway wrote: post #15

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?

Is Matz still there?

Matz might have been on the payroll, but he never really worked for Heroku.

Re: Heroku: We’ve Heard Your Feedback

#110

Post by freedomben »

alfiedotwtf wrote: post #80
freedomben wrote: post #49

Earlier quoted context omitted.

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

Devs use LinkedIn for blog posts? Are they using it as way to get other devs to read it, or as a way to get potential employers to notice them? Tbh, I don't a single dev who uses LinkedIn unless they looking for a new role I.e they're certainly not using LinkedIn as a dev-oriented news feed

Yes, surprisingly many of the devs used LinkedIn for blog posts. The type of blog posts that they did were somewhat different as well. It was normal to see posts that had to do with engineering culture and how to structure an engineering department, things like that. They would also often talk about technology from a high level. For example "why I think vert.x is the future of Java high performance programming", or something like that.
Post reply on HN