This literally says nothing - are we supposed to infer that they are putting the product into maintenance mode and will no longer be developing new features for it? This is a masterpiece of corporate nullspeech.
> with an emphasis on maintaining quality and operational excellence rather than introducing new features it sounds pretty clear that it's in maintenance mode
An Update on Heroku
161–170 of 366 posts
Re: An Update on Heroku
#162Earlier quoted context omitted.
Build.io came out of this exact problem a few years ago (I joined in 25Q4) - trying to be what Heroku could have been if it had continued to evolve. We offer the same default simplicity/speed, but with the ability to go deeper once teams hit scale, cost, or workflow limits. Plus a pricing model that stays understandable and improves as teams scale rather than punishing them for it. Fair warning: the website is pretty…
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
Re: An Update on Heroku
#163Re: An Update on Heroku
#164Re: An Update on Heroku
#165Earlier quoted context omitted.
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…
Often "nothing is changing" ends up being more literal than the founders realize or intend. Acquisitions by big companies tend to slow the development to a crawl as development bureaucracy takes over. When a great product is practically frozen in time it stops being great in 5-15 years as the rest of the world passes them by.
Re: An Update on Heroku
#166I'd be glad to stand corrected but AFAICT this is the only sentence that describes the change. All other say "nothing is changing in [some area]".
Trying to downplay something to that extent immediately raises suspicious that this something (the change) is much more profound that what is stated.
Re: An Update on Heroku
#167I wonder how much money Salesforce would need to sell what's left of Heroku to a better steward.
My money is on holding companies like IAC buying the brand first through financial engineering and restructuring finances initially. They would load it up with debt like they did with the sporting goods store in Sopranos.
Afterward, they would sell it to a Euro-based caretaking company like Bending Spoons, with a focus on maintenance engineering rather than innovation engineering.
Re: An Update on Heroku
#168"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.
Re: An Update on Heroku
#169Earlier quoted context omitted.
I remember feeling the same way about Slicehost back in the day after Rackspace acquired them. Loved Slicehost. Not too long after though, Digital Ocean appeared with everything I loved about Slicehost and has kept getting better ever since. I feel like that's Fly.io now. They took all of the great things about Heroku but also dramatically improved and added new capabilities...while improving on pricing, particularly…
> They took all of the great things about Heroku but also dramatically improved and added new capabilities I also love Fly, but they were missing easy managed databases (which always seemed like the main reason to use Heroku to me). And now they have them they're very expensive (even compared to Heroku). Which is a shame because their compute is very cheap.
We're doing Managed Postgres now (MPG), which is what we should have done to begin with, but it took us for-ev-er to get here.
Re: An Update on Heroku
#170Earlier quoted context omitted.
Build.io came out of this exact problem a few years ago (I joined in 25Q4) - trying to be what Heroku could have been if it had continued to evolve. We offer the same default simplicity/speed, but with the ability to go deeper once teams hit scale, cost, or workflow limits. Plus a pricing model that stays understandable and improves as teams scale rather than punishing them for it. Fair warning: the website is pretty…
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