Hacker News new | ask | show | jobs
by salman89 4872 days ago
Most people are going to come here and mention how they are not planning on fixing the problem.

Put it into context. Heroku made this change 3 years ago, and also has had no issues admitting the change to users. Their documentation has lagged far behind and I believe they will be more transparent in the future. This is an engineering decision they made a long time ago that happened to get a lot of PR in the past 24 hours. Until there is a business reason (losing customers), I don't see them "fixing" the problem.
1 comments
twog 4872 days ago
I think this PR has already hurt Heroku & caused them to lose customers.
link
WestCoastJustin 4872 days ago
The only thing worse than being talked about is not being talked about - OW

You are almost investing in heroku by using their stack and tool chain, it isn't easy for well established customers to just up and move. This is probably a PR win for them, rather than a loss. Truth be told, it will be how they handle this in the coming months that will make them win/lose customers.

link
camus 4871 days ago
If you are locked in the trunk with any cloud solution , then you are a bad programmer/syst admin/whatever taking bad decisions, period.

You should be able to move your project infrastructure quickly from a service to another ,if you cant to that, well too bad when your infrastructure fails...

link
res0nat0r 4872 days ago
How many customers are running on a stack that old that are at the scale being complained about? It is probably cheaper to tell them to upgrade if they want better performance, or if they dont want to/ can't then they unfortunately can't be officially supported.
link
badgar 4872 days ago
Cedar doesn't fix this for Rails. It helps marginally.
link