3 ms·

I understand this is news for a few months now but still, such a hostile way to just unplug projects and to an extent, the history of the web. I doubt Salesfor

I understand this is news for a few months now but still, such a hostile way to just unplug projects and to an extent, the history of the web. I doubt Salesforce is struggling with cash not to let these projects stay online on a “read only” mode.

clintonb 4y ago
What would you propose they do differently?
- simonw 4y ago
  The single biggest thing would be to suspend the websites but NOT delete the underlying data - for at least a month, ideally six. That way all of the people who missed the news about Heroku and first heard about it when sites they were using stopped working would have a fighting chance to recover their data before it vanished. Even better: Salesforce could have actually invested resources in Heroku (instead of effectively feature-freezing it a few years ago) such that the thing where the free tier acts as a major funnel for attracting paying customers continued to work, as it had for most of the lifetime of the service.
  - vachina 4y ago
    If you have a Heroku instance you definitely have a local copy of your code stashed somewhere.
    - Raed667 4y ago
      some projects are +10 year old. People will go through multiple laptops in that time. if your project used heroku directly without any github integration then they effectively were also your source control.
    - simonw 4y ago
      The PostgreSQL data is a much bigger problem than the code.
  - ehPReth 4y ago
    Completely agree. Scale down to zero and turn off (access to/entirely) databases but do not purge any data for 6m or so, hopefully one last chance and enough time for someone to notice and go "oh no!" and pay up/export data. Just shutting it down and deleting after notifying via email (did notices go to junk? etc?) is kinda shitty to do.