Skip to content

Comment on Security Release FAQparent

Comments

> An more detailed writeup, but hardly satisfying. Like most of Heroku's technical choices made in the name of "simplicity" and "robustness."

> But I guess I should accept that Heroku will never be a technically impressive PaaS provider. Just the one I hear about the most.

Many people care about robustness the most, bar none. We can't have everything all the time, just as Linux doesn't implement a ton of stuff seen on old mainframe kernels. Many things have not caught up with Tandem Computers, either -- re-inventing all that kind of stuff, even if only to recast it in modern settings, is time consuming, especially if one wants to keep the 'weird factor' low, and mitigate lock-in. There's a non-zero risk of things going horrifically wrong, too.

The best I can do is let folks appreciate the difficulty, but that's really in part a coded way of saying "not a three-line fix, so if this is a deal breaker, move on." If you thought it was also interesting, then all my objectives for that writing are met.

So, sorry in advance if a lot of Heroku things aren't very impressive, and I try to make things a tiny bit better day by day. Maybe one day you'll be impressed.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.