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

261–270 of 366 posts

Re: An Update on Heroku

#261

Post by almost »

gonational wrote: post #254
Folcon wrote: post #241

Earlier quoted context omitted.

I'm just going to chime in here and say thank you, there still really isn't in my mind a comparable offering to heroku's git push and go straight to a reasonable production I honestly find it a bit nuts, there's offerings that come close, but using them I still get the impression that they've just not put in the time really refining that user interface, so I just wanted to say thank you for the work you and the GP di…

This! It absolutely boggles my mind that nothing else exists to fill this spot. Fly and others offer varying degrees of easier-than-AWS hosting, but nobody offers true PaaS like Heroku, IMHO.

For me Northflank have filled this spot. Though by the time I switched I was already using Docker so can't speak directly to their Heroku Buildpack support.

Re: An Update on Heroku

#263

Post by xeromal »

codegeek wrote: post #119
bearjaws wrote: post #88

The downfall of Heroku should be studied, they had lightning in a bottle and blew it. Salesforce acquired them and just let it die, baffling.

Nothing to study. A common scenario when a mega corp acquires an incredibly successful startup and then lets it die. Happens more often than not. This is why I chuckle when I see an acquisition and the founders claim "Nothing is changing. We are not going anywhere" . There may be exceptions but the moment a hugely successful company like heroku gets acquired, you know it's most likely game over. To their credit, they…

Heroku was bought by salesforce when it was only 3 years old.

Re: An Update on Heroku

#264

Post by [deleted] »

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…

[deleted]

Re: An Update on Heroku

#265

Post by franciscop »

paxys wrote: post #139
simonw wrote: 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.

If any Heroku customer is reading this and not immediately going "we need to move off Heroku ASAP" all future problems are their own fault.

I loved Heroku, but moved away a couple of years back. Tried 3 major "alternatives" (dokku, Render, Fly.io), and the big clouds, and the only thing that made me happy at the end was Coolify. I do keep Netlify for FE-only projects though.

Re: An Update on Heroku

#266

Post by dpe82 »

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…

Having been on a bigco team that underwent the same sort of headcount growth in a very short time I have to imagine that "more than tripling our headcount in that first year" was likely more a driver of the inability to keep up than a solution. That's not a knock on the talents of anyone hired; it's just exceedingly difficult to simultaneously grow a team that fast and maintain any kind of velocity regardless of the complexity of the problems you're trying to tackle. The culture and knowledge that enabled the previous team's velocity just gets completely diluted.

Re: An Update on Heroku

#267

Post by deepsun »

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…

I worked with some of the folks from there, and honestly you make it sounds like tech debt is inevitable consequence haunting projects from year one.

I disagree, I think the folks just did a sloppy job of "let's bungee strap it all together" for speed, instead of more serious planning and architecturing. They self-inflicted the tech debt on them and got drowned in the debt interest super fast.

Re: An Update on Heroku

#268

Post by TranquilMarmot »

deepsun wrote: post #267
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…

I worked with some of the folks from there, and honestly you make it sounds like tech debt is inevitable consequence haunting projects from year one. I disagree, I think the folks just did a sloppy job of "let's bungee strap it all together" for speed, instead of more serious planning and architecturing. They self-inflicted the tech debt on them and got drowned in the debt interest super fast.

Sure, but that bungee strapped slop got them pretty damn far

Re: An Update on Heroku

#269

Post by fragmede »

gonational wrote: post #254
Folcon wrote: post #241

Earlier quoted context omitted.

I'm just going to chime in here and say thank you, there still really isn't in my mind a comparable offering to heroku's git push and go straight to a reasonable production I honestly find it a bit nuts, there's offerings that come close, but using them I still get the impression that they've just not put in the time really refining that user interface, so I just wanted to say thank you for the work you and the GP di…

This! It absolutely boggles my mind that nothing else exists to fill this spot. Fly and others offer varying degrees of easier-than-AWS hosting, but nobody offers true PaaS like Heroku, IMHO.

vercel goes a step further, and (when configured this way) allocates a new hostname (eg feature-branch-add-thingg.app.vercel.example.com) for new branches, to make testing even easier.

Re: An Update on Heroku

#270

Post by elondemirock »

The simplicity it brought at the time to hand-jammed and complex processes was nothing short of exemplary. They set the bar on how streamlined application deployment can be and a great UI to go along with it.

Heroku may die but the ideas Heroku executed on and brought to life will continue to prosper... so long Heroku!

Post reply on HN