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

An Update on Heroku

heroku.com

Post reply on HN
Print view View original

211–220 of 366 posts

Re: An Update on Heroku

#211

Post by bgentry »

drewda wrote: post #195
bgentry wrote: post #187

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?

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!

Re: An Update on Heroku

#212

Post by krashidov »

mplewis wrote: post #198
krashidov wrote: post #189

Earlier quoted context omitted.

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.

haha we actually launched it today. Point taken though! It's not a video though just an interactive widget. Instead of scrolling you press enter. Once we launch I'm sure we'll have something more traditional

Re: An Update on Heroku

#213

Post by cruffle_duffle »

All I’m going to say is if your press release is titled “an update on heroku” instead if something exciting it means you aren’t delivering happy news that is good for the user.

I bet I’m right. Haven’t read the article or comments, I’m just posting this comment to see if I’m proven right or wrong.

Re: An Update on Heroku

#214

Post by altairprime »

glenngillen wrote: post #201
altairprime wrote: post #140

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…

Absolutely none of this is true. What was the PaaS Heroku was apparently beating at the time of the acquisition?

Noted. Please accept my apologies and retraction.

Re: An Update on Heroku

#216

Post by BoorishBears »

satvikpendem wrote: post #205
BoorishBears wrote: post #203

Earlier quoted context omitted.

"Depends on what you used it for" applies to just about any platform. Realistically, self-hosting the PaaS defeats the purpose of a PaaS for the crowd Heroku was attracting.

Heroku was one of the first to have that seamless UX, only after which others like Fly or Render or Railway came to copy it. I wager people were primarily attracted to that user experience and only minimally cared that it was fully hosted versus not, because there was also AWS at that time.

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

Re: An Update on Heroku

#217

Post by rubslopes »

pelagicAustral wrote: post #73

I used to be a fan of Heroku when I started working web apps... The deployments were so easy, but I became numb to the actual task of dealing with the complexities of a deployment, when they killed the free tier I struggled for a while... I work with Rails, and I used to bitch a lot about how hard it was to deploy an app, but in retrospective I kind of thank Salesforce for murdering their own product. Now I deploy at…

I've been using Coolify for deploying my webapps for about 3 years, it has a good web UI.

Re: An Update on Heroku

#218

Post by satvikpendem »

BoorishBears wrote: post #216
satvikpendem wrote: post #205

Earlier quoted context omitted.

Heroku was one of the first to have that seamless UX, only after which others like Fly or Render or Railway came to copy it. I wager people were primarily attracted to that user experience and only minimally cared that it was fully hosted versus not, because there was also AWS at that time.

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.

Re: An Update on Heroku

#219

Post by ptdorf »

Aurornis wrote: post #194
bgentry wrote: post #187

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

The cancer of corporations: bureaucracy.

Re: An Update on Heroku

#220

Post by asenchi »

bgentry wrote: post #187

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…

It remains the greatest engineering team I've ever seen or had the pleasure to be a part of. I was only there from early 2011 to mid 2012 but what I took with me changed me as an engineer. The shear brilliance of the ideas and approaches...I was blessed to witness it. I don't think I can overstate it, though many will think this is all hyperbole. I didn't always agree with the decisions made and I was definitely there when the product stagnation started, but we worked hard to reduce tech debt, build better infrastructure, and improve... but man, the battles we fought. Many fond memories, including the single greatest engineering mistake I've ever seen made, one that I still think about until this day (but will never post in a public forum :)).

It was a pleasure working with you bgentry!

Post reply on HN