back

by craigkerstiens·4y ago·view on hn ↗
There are some that have emulated it, but the team that was there and created Heroku cared deeply about developer experience. When you just "clone" that you miss pieces, one PM friend that I worked with at Heroku called them papercuts. We would obsess over such things and the quality of something being shipped.

Even now if you emulate that it's one thing, but Heroku has been frozen in time for at least the last 5 years, maybe closer to 7-8 years. There was more to do and more to improve and advance, and it stalled out for reasons. Now just being a clone wouldn't be enough you need to continue advancing the experience.

1 comments
Sorry, I’m not proposing a team that not care clone it. I’m hoping that a team that cares very much do so. I agree that UX is the differentiator here.

What I am challenging is the idea that the last 8 years of missed advancement are a requirement. I’m sure there’s necessary under the good improvements; I question if there’s necessary user facing ones. Lots of people (me at least) are very happy with Heroku’s exact current feature set, minus the recent and future stability issues. We just want that to exist forever.