I think its impossible for the Herokus and the digital oceans of the world to survive in the cloud world. They might be able to create better experience for customers but noone can match the networking that AWS, GCP and Azure can provide. Low latency will always win over better developer experience.
The blog author isn’t understanding it but it’s quite simple: the product only matters in the context of large enterprise customers.
The large customers still get what they want as long as the ask isn’t too big and that’s why you see new features even though the product is in maintenance mode.
It’s just in coma, slowly dying away on a respirator. Some relatives irrationally keep paying the hospital to keep the patient alive, but the doctors just wait until they can finally pull the plugs and use the bed for someone with actual chances of survival.
I think the downhill slide started when they introduced the "Private Space Peering". It is a wrapper on top of AWS VPC, but it was something like $1000 a month several years ago. It also was gating larger instances and other important features.
So few people used it. I guess this provided a negative signal to their management about the adoption rate of new features. And then everything eventually just died.
What a weird article that's microanalysing language in Heroku's blog posts. I mean times are such that pivot-churn is becoming business as usual for most outfits these days so I wouldn't put any stock on C-Suite verbiage.
I think its impossible for the Herokus and the digital oceans of the world to survive in the cloud world. They might be able to create better experience for customers but noone can match the networking that AWS, GCP and Azure can provide. Low latency will always win over better developer experience.
Five bucks it’s this:
Management: “we’re going into maintenance mode”
Devs: “You mean we get to work on whatever we want?!”
Next week: “we are right-sizing the organization”
The blog author isn’t understanding it but it’s quite simple: the product only matters in the context of large enterprise customers.
The large customers still get what they want as long as the ask isn’t too big and that’s why you see new features even though the product is in maintenance mode.
Heroku has been going downhill ever since Salesforce bought them.
Actually the opposite: they came into their prime after the acquisition. Probably not due to Salesforce, but still.
I can't believe that it has been over 15 years ... https://news.ycombinator.com/item?id=1982489
Strong disagree. They didn’t even invent buildpacks until 2011, the year after the acquisition.
Momentum??
It’s just in coma, slowly dying away on a respirator. Some relatives irrationally keep paying the hospital to keep the patient alive, but the doctors just wait until they can finally pull the plugs and use the bed for someone with actual chances of survival.
I think the downhill slide started when they introduced the "Private Space Peering". It is a wrapper on top of AWS VPC, but it was something like $1000 a month several years ago. It also was gating larger instances and other important features.
So few people used it. I guess this provided a negative signal to their management about the adoption rate of new features. And then everything eventually just died.
The related discussion on one of the mentioned blog posts:
An update of Heroku
https://news.ycombinator.com/item?id=46913903
What a weird article that's microanalysing language in Heroku's blog posts. I mean times are such that pivot-churn is becoming business as usual for most outfits these days so I wouldn't put any stock on C-Suite verbiage.