Heroku used to be so cool: such a developer-friendly company, offering generous free tiers and easy ways to deploy and maintain projects.
SalesForce has really done a number on them. So sad to see 😞
Heroku is transitioning to a sustaining engineering model focused on stability, security, reliability, and support. Heroku remains an actively supported, production-ready platform, with an emphasis on maintaining quality and operational excellence rather than introducing new features. We know changes like this can raise questions, and we want to be clear about what this means for customers.
There is no change for customers using Heroku today. Customers who pay via credit card in the Heroku dashboard—both existing and new—can continue to use Heroku with no changes to pricing, billing, service, or day-to-day usage. Core platform functionality, including applications, pipelines, teams, and add-ons, is unaffected, and customers can continue to rely on Heroku for their production, business-critical workloads.
Enterprise Account contracts will no longer be offered to new customers. Existing Enterprise subscriptions and support contracts will continue to be fully honored and may renew as usual.
Why this change
We’re focusing our product and engineering investments on areas where we can deliver the greatest long-term customer value, including helping organizations build and deploy enterprise-grade AI in a secure and trusted way.
Interesting little experiment tonight:
I asked ChatGPT to edit a Pokemon save file so that I could do an egglocke in Pokemon Gold.
Using Agent Mode and a set of parameters (no legendaries, first-stage only, etc.), it filled two boxes with random pokemon eggs.
#ChatGPTEggLocke
@kentcdodds When your index fills up due to overflow and all your code starts to fail to insert anything, you get to remember all the neat stuff you built and how important it is 💖
If you use UUIDs you don’t ever get to resolve incidents on Saturday mornings ☹️
@kentcdodds Then I guess it comes down to whether it will be cost effective and scalable enough for your use case to do so, and if you’ve got the know-how to be able to keep it secure.
Kinda sounds like a use case that Heroku or DigitalOcean could fill.
@DThompsonDev Pull request is titled: “Init”, and it’s got like a couple commits.
First comment: “You need to add node_modules to .gitignore, remove all this stuff from the commit, and try again.”