6 ms·
Heroku seemed like it was going to be the future back then. Every time I find myself struggling to understand some nonsense in Azure I dream of the simpler fut
by dec0dedab0de 20d ago
Heroku seemed like it was going to be the future back then. Every time I find myself struggling to understand some nonsense in Azure I dream of the simpler future we lost.
- jpb0104 20d agoI've got to give credit where it is due... It really feels like Laravel Cloud picked up where Heroku left off. Or at least is trying to.
- rietta 20d agoThey got painfully expensive and then acquired. I still remember the arguments with clients and finally went all in AWS ECS, which is still quite pricey but clients seem to complain less about the Amazon bill then they did about Heroku.
- mermadicsolutio 19d agoOther than the pricing, for something built for simplicity, i always found their config method bit weird. Maybe it's just me b/c I first learned the aws stack, and got tired of managing EKS
- cgarvis 20d agoFly.io brings back some of that easy of deploy.
- drob518 20d agoYep, agreed. Fly.io is the closest to Heroku that I’ve found.
- kestrel-robotic 19d agoCaprover for me, but fly.io is pretty cool, reminds me of flynn.io
- nkmnz 19d agoEspecially the pricing is equally joyous.
- vrosas 19d agoGive Cloud Run a try if you haven't. It's basically serverless done right.
- nunez 19d agoSucks that it didn't become that. "heroku up" or "cf push" (Heroku kind of sort of invented build packs) was hella addictive. Shoot, I'm sad that Docker didn't become the way to run containers. compose/swarm is still light years easier than Kubernetes I guess Heroku ran so that Vercel could fly?
- mermadicsolutio 19d agoYeah I don't see a reason to use k8s if not on cloud, and k8s on cloud is even more complex. Compose is still the right size for one box, that one command does all was really nice to have