Live data from Hacker News

An Update on Heroku

heroku.com

191–200 of 366 posts

Re: An Update on Heroku

#191
post #47

Earlier quoted context omitted.

Moved from heroku to fly.io three years ago and I don’t regret it, great platform occasionally goes down and requires a bit of attention but the support forum is great

It didn't seem quite as fire-and-forget as doing `Heroku create` when I tried to use it 3-4 years ago, especially the database setup. Do you use their Postgres offering?

No my one is a simple ruby sinatra app with no DB. Yeah unfortunately it wasn’t super reliable as heroku but they’re getting better at keeping the instances up

Re: An Update on Heroku

#192
post #10

"We know changes like this can raise questions, and we want to be clear about what this means for customers." Proceeds to not be clear about what this means for customers.

Was clear to me. If I was looking at using them, I wouldn’t. If I was already using them, I’d stop. They seem dedicated to supporting the slow extinction so it doesn’t have to be a fire drill exit, but how do you sleep at night knowing they’re playing with matches.

Re: An Update on Heroku

#193
I used Heroku extensively before AWS reached its current level of maturity. Heroku made it incredibly easy to create cool apps. When Salesforce acquired it, and knowing a lot about Salesforce, I expected tight integration to address use cases where Apex is too limited (Apex being Salesforce's native language). There were (and still are) numerous such use cases. Unfortunately, this never materialized, and Salesforce gradually shifted away from a dev-first platform toward click-based config and heavy reliance on middleware for all kind of integrations.

It's been a butchered acquisition and missed opportunities along the way. And now it ends up just like Microsoft's Skype.

Re: An Update on Heroku

#194

As somebody whose first day working at Heroku was the day this acquisition closed, I think it’s mostly a misconception to blame Salesforce for Heroku’s stagnation and eventual irrelevance. Salesforce gave Heroku a ton of funding to build out a vision that was way ahead of its time. Docker didn’t even come out until 2013, AWS didn’t even have multiple regions when it was built. They mostly served as an investor and le…

Thanks for sharing your story. Those early days of using Heroku were really enjoyable for me. It felt so promising and simple. I remember explaining the concept to a lot of different people who didn't believe that the deployment model could be that simple and accessible until I showed them.

Then life went on, I bounced around in my career, and forgot about Heroku. Years later I actually suggested it for someone to use for a simple project once and I could practically feel the other developers in the room losing respect for me for even mentioning it. I hadn't looked at it for so long that I didn't realize it had fallen out of favor.

> That time coincided with the founders taking a step back, leaving a loss of leadership and vision that was filled by people more concerned with process than results

This feels all too familiar. All of my enjoyable startup experiences have ended this way: The fast growing, successful startup starts attracting people who look like they should be valuable assets to the company, but they're more interested in things like policies, processes, meetings, and making the status reports look nice than actually shipping and building.

Re: An Update on Heroku

#195

As somebody whose first day working at Heroku was the day this acquisition closed, I think it’s mostly a misconception to blame Salesforce for Heroku’s stagnation and eventual irrelevance. Salesforce gave Heroku a ton of funding to build out a vision that was way ahead of its time. Docker didn’t even come out until 2013, AWS didn’t even have multiple regions when it was built. They mostly served as an investor and le…

Thanks for a capsule tour through Heroku!

FWIW, the team that eventually created "Docker" was working at the same time on dotCloud as a direct Heroku competitor. I remember meeting them at a meet-up in the old Twitter building but couldn't tell you exactly which year that was. Maybe 2010 or 2011?

Re: An Update on Heroku

#196

Earlier quoted context omitted.

As a former enterprise person, this clearly states “exiting growth cycle into low-staffing maintenance mode”; Salesforce must have bought them to kill a price-beating competitor to multi-year Salesforce PaaS contracts, same as Okta did with Auth0. Investors are typically-majority short-sighted and only care about growth-cycle revenue, so once they reached market saturation, they were ripe and duly reaped. So long, He…

You are saying the plan was to buy a "price-beating competitor", invest in them for 16 years, and then finally pull the rug out now?

They’re not competition if you own them! Typepad continued for over a decade after it was purchased. Auth0 is still in maintenance mode afaik. It can last as long as revenue pays for the FTE to maintain it, or until corporate reallocated the FTE to higher revenue-per-FTE-hour opportunities.

Re: An Update on Heroku

#197

Earlier quoted context omitted.

It means: go elsewhere, they're dead.

What's the best alternative?

We saw this coming (like most people) a while ago when Heroku started flaking without status updates, and moved part of our workload to Fly. We ended up moving off Fly as well (significant unreliability and just some very strange network load balancer issues that would cause us downtime) and went to Railway, and that's been fantastic so far. We've moved our whole workload onto it.

Re: An Update on Heroku

#198
post #175

Earlier quoted context omitted.

Thanks for reminding me that slack is owned by Salesforce. What are we going to use when slack turns to shit, IRC again maybe?

type.com (full disclosure I am one of the cofounders)

You gotta fix the home page. I'm not sitting through a movie trailer to find out how your chat app works.

Re: An Update on Heroku

#199

Earlier quoted context omitted.

You are saying the plan was to buy a "price-beating competitor", invest in them for 16 years, and then finally pull the rug out now?

Reminds me of https://youtu.be/T2BY8zZ1CTM?si=XDroWqVD-pElN9si

that was great!

Re: An Update on Heroku

#200

Earlier quoted context omitted.

You are saying the plan was to buy a "price-beating competitor", invest in them for 16 years, and then finally pull the rug out now?

Reminds me of https://youtu.be/T2BY8zZ1CTM?si=XDroWqVD-pElN9si

[flagged]
Post reply on HN