Heroku is a remote-friendly team.
Q: "How do you do a search and replace for a string in VI"
Me: I cant recall right now, i'd just google it"
Someone doesn't need to be "a stupid MBA" to have made this decision (in fact my guess would be it involved many cross functional and leadership perspectives given its nature).
Also, this is quite possibly something necessary for the future continued health of the business and the jobs it supports. If so, I'd consider it anything but stupid.
It seems to me like there’d be a big market for an identical feature by feature Heroku “clone” with a more dedicated (from the outside looking in) team. No more features, no less, just exactly what Heroku did but without the intent to shut down. What’s preventing that from existing?
It was clear even before their horribly bungled GitHub security incident that Heroku was on life support at best and it's been a long time since "Heroku" was the answer to "What PaaS should I use?".
The beancounters took control a while back and are sucking all they can out of it before they discard it's empty shell.
Having Heroku as your PaaS provider seems like a bad business decision at this point. You are just begging to have the rug pulled out from under you.
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.
Blog post says "Salesforce has never been more focused on Heroku's future." but this looks like they are just keeping the lights on by deprecating and keeping security up to date. Which isn't bad if the product has reached maturity but I wonder if these really are the most important features users ask for.
Why does the feedback link on the blog post go to a personal LinkedIn page? What is wrong with these companies?
Watching for feedback here, but it's nice to know when I'm getting reachouts on product feedback directly who is touching base. Linked-in is great for that. But also, if you want to provide feedback we launched the roadmap on github if that's your preference. Trying to cover both kinds of customers.