Hacker News Reader

Comment by evtothedev | Hacker News Reader

Does anyone else find the roadmap to be really uninspiring? Every tasks seems either like housekeeping ("Migrate from Github OAuth to Github App Model") or like far-too-late table stakes ("Support HTTP/2").

What am I supposed to get inspired about on this page?

For items that look like they ?might? be exciting, they seem hidden behind vagueness: "Official Cloud Native Buildpacks for Heroku languages"

Contrast this with Render's public roadmap: https://feedback.render.com/

That has nice, plain english. I know what they're building, and I can start dreaming about what I might build with it.

View on HN

I'm with you, but to play devil's advocate...

1. Heroku already has most of the features on Render's roadmap

2. It's clear Heroku (well, Salesforce) is going all-in on Enterprise, and Enterprise doesn't reward cool new features. They like stability (and jargon-y words).

Heroku doesn't handle distributed Elixir nor static sites. Render does.

Could you jump in on the cloud native buildpack issue above and ask for clarification? Goal of the public roadmap is to gather input and feedback and make it better.

Yeah it was a bit disappointing to see it. For me I was looking for two important features that is essential for a European SaaS company or in the Enterprise segment:

1) No plans to do regional Postgres backups. Today PG backups are transferred out of the database region and to us-east-1. This is problematic for anyone who takes GDPR seriously and unacceptable for any customer with strict compliance requirements.

2) No possibility of wildcard + ACM TLS. We have to implement our own cert automation using Let's Encrypt instead of relying the fully functional Heroku ACM because we also need to use a wildcard cert. This is something that most SaaS vendors would require.

Heroku are aware of both these issues. For #1 it seems like they don't care. For #2 it seems like it is a result of legacy infrastructure.

Reply on news.ycombinator.com