That's different. Heroku itself was a massive success. The Salesforce management completely screwed up the department after the acquisition.
That's on Salesforce not Heroku. Heroku left the building already.
That's on Salesforce not Heroku. Heroku left the building already.
(Although I would argue that Salesforce was also responsible for creating most of what we love about Heroku. That acquisition happened far earlier than people realize. They're also almost entirely responsible for its downfall.)
EDIT: Craig is right below (and he pretty much always is). When I said "created" I really meant in terms of giving them enough financial resources to keep building. SFDC exerted no influence in terms of product decisions early on (so far as I know). Re-reading my post I see that wasn't clear.
GitHub is an amazing parallel, folks feel that Microsoft turned around GitHub, but actions and much of the GitHub turn around happened long before the acquisition. Those sort of things take years, you should mostly try to judge a top down influence 4-6 years after they were there.
Interesting - someone at either MS or Github told me that the Azure DevOps team moved over to GitHub to create Actions. But maybe I misheard or both versions are true.
- That Jason Warner, Max Schoening, and a brains trust of Heroku Product & Design leadership jumped ship to GitHub. After they got there they continue their run of product success and innovation and launch the next platform innovation for GitHub. Which also just happens to be yet another way to run code as a service.
- The ADO team join GitHub, and then pivot into a whole new and foreign area.
People can make their own judgements on which of these is the most likely option.