I don't buy this, of course if you run the NYT infrastructure you don't go for Heroku. Heroku is still the best for smaller projects (and medium sized dependin

I don't buy this, of course if you run the NYT infrastructure you don't go for Heroku. Heroku is still the best for smaller projects (and medium sized depending on the type of the workload) and devs that are not fully devops. Sure, if you have a previous project where you can copy pasta your Terraform and Kubernetes setup from, you can start your infra just as fast, but otherwise heroku app:create and git push heroku master is still way faster to start hustling. Everyone compares invoices between e.g. AWS and Heroku, but do they ever take into account the cost of the ops team when they switch to AWS? If the bill was 7 figures on Heroku with no devops, how many senior devops does it take to get the same spend with AWS? How about productivity loss if deploying is not as easy as it was before? I think saying something is dead because it doesn't work in all use cases is not fair.