3 ms·
> This works for future customers, since once Heroku makes these documentation changes, everyone who signs up will understand exactly how routing works. But it
by jacques_chester 14y ago
> This works for future customers, since once Heroku makes these documentation changes, everyone who signs up will understand exactly how routing works. But it does nothing to address the time and money that existing customers have spent over the past few years. What does Heroku owe them?
Lawyers -- well, judges really -- are good at coming up with answers for this exact sort of question.
I am not being facetious. There are legal rules for assessing losses in even very complex, very entangled situations. If you feel Heroku has dudded you, find a torts lawyer.
Heck, Salesforce.com have deep pockets. Round up a few other $20k/month customers and start a class action.
Web companies need to realise that boring old-fashioned rules like "your claims should not be misleading" apply to them too.
(IANAL, TINLA)
- chacham15 14y agoummmmm......salesforce bought heroku
- LeafStorm 14y agoThe implication there was that because Salesforce owns Heroku, they would be able to pay up major cash if Rap Genius got some other Heroku customers involved in the lawsuit.
- res0nat0r 14y agoI don't think you can sue Heroku because it was "slow". Were any SLAs offered by Heroku explicitly not met? If so that's a different story. If AWS was able to be sued by every customer who didn't understand how their infrastructure config worked with the underlying EC2 network, or did something incorrectly for a time due to a documentation mistake there would be more lawyers working at Amazon than engineers.
- brown9-2 14y agoSeems like at most you could sue to get back some of what you paid them.
- neerajdotname2 14y agoDo not treat loss as only the money lost. Lost customers are priceless and one can put a high price tag to that. Also loss in productivity because their documentation was misleading.