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?
An Update on Heroku
191–200 of 366 posts
Re: An Update on Heroku
#192"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
#193It'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
#194As 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…
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
#195As 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…
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
#196Earlier 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?
Re: An Update on Heroku
#197Earlier quoted context omitted.
It means: go elsewhere, they're dead.
What's the best alternative?
Re: An Update on Heroku
#198Earlier 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)