Live data from Hacker News

An Update on Heroku

heroku.com

221–230 of 366 posts

Re: An Update on Heroku

#221
post #195

Earlier quoted context omitted.

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?

Yep, that team did great work. I remember having lunch at the Heroku office with the dotCloud team in 2011 or 2012 and also Solomon Hykes demoing Docker to us in our office’s basement before it launched. So much cool stuff was happening back then!

I remember Solomon's demoing at All Hands... it was such a crazy time for tech and innovation.

Re: An Update on Heroku

#222

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?

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.

Auth0 still has a ton of people working on it at Okta. If they’re facing execution problems, it’s not due to a lack of resources.

Re: An Update on Heroku

#223
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.

I worked at Pardot around the time Salesforce started using this same language in internal announcements about Pardot.

Our Pardot leadership translated for us and provided the necessary context: Pardot is being killed. The plan was to start building the product that would replace it, stop selling new contracts, rename Pardot in the meantime so the change wouldn't be as noticeable, and in a timeline of "by 10 years from now" Pardot wouldn't exist anymore.

This is Salesforce for "last call for the lifeboats, we're gonna capsize the boat."

Re: An Update on Heroku

#224

Earlier quoted context omitted.

Yep, that team did great work. I remember having lunch at the Heroku office with the dotCloud team in 2011 or 2012 and also Solomon Hykes demoing Docker to us in our office’s basement before it launched. So much cool stuff was happening back then!

I remember Solomon's demoing at All Hands... it was such a crazy time for tech and innovation.

Oh hey Curt!! Remember, you are not a monitoring system :)

Re: An Update on Heroku

#225
post #170

Earlier quoted context omitted.

Do you care to show prices? The true benefit of heroku for me was really predictable pricing model. Build.io website doesn’t have it on mobile site at all. I don’t want to look at demo, i want to hook up my credit card, set a monthly budget and explore

llIIllIIllIIl & runako give me an email on steven[at]build.io and I'll share. As mentioned, we stripped the site back while we overhaul and we certainly didn't expect this today!

To be clear, you just answered "Do you care to show prices?" with No.

Re: An Update on Heroku

#227

Earlier quoted context omitted.

How do you think self-hosting affects that seamless UX they value.

As I said, the correct software on top handles it all for you. I don't think you've actually tried Dokploy.

Dokku is better. And neither is what Heroku's bread and butter customer needs.

But alas, my interest in painstaking explaining why self-hosting is fundamentally incompatible with a product who's value prop was "nothing to install" is waning.

Have a good one.

Re: An Update on Heroku

#228

Earlier quoted context omitted.

As I said, the correct software on top handles it all for you. I don't think you've actually tried Dokploy.

Dokku is better. And neither is what Heroku's bread and butter customer needs. But alas, my interest in painstaking explaining why self-hosting is fundamentally incompatible with a product who's value prop was "nothing to install" is waning. Have a good one.

You and I simply have different opinions on what Heroku's value proposition was, because, again, AWS was also right there and also was "nothing to install." Therefore Heroku was used primarily for its dead simple UX, something which is replicated even in a self-hosted environment, because, again, the value prop was never about PaaS or self-hosting, it was always about the user experience.

Have a good weekend.

Re: An Update on Heroku

#229

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…

As far as the Salesforce acquisition goes, I'd be curious to see who made the decision to put Heroku into maintenance only mode.

I worked for a different part of Salesforce. I don't really feel like Salesforce did a ton of meddling in any of its bigger acquisitions other than maybe Tableau. I think the biggest missed opportunity was potentially creating a more unified experience between all of its subsidiaries. Though, it's hard to call that a failure since they're making tons of money.

It could be a case of post-founder leadership seeing that there's not a lot of room for growth and giving up. That happens a lot in the tech industry.

Post reply on HN