TLDR: RapGenius (YCS11), in a painful attempt to remain relevant, decides to sue their web host for running their slow code slowly.
Coding Cloud Heroku May Face Lawsuit Over Bait-and-Switch Claims
51–60 of 100 posts
Re: Coding Cloud Heroku May Face Lawsuit Over Bait-and-Switch Claims
#52It really disgusts me how quick people are to bite the hand that feeds them. Heroku is not perfect, but they give a whole lot more value than they charge for. As unlikely as it is, I hope that Heroku terminates the account of anyone that joins the class action against them.
> As unlikely as it is, I hope that Heroku terminates the account of anyone that joins the class action against them. It would be hard to give worse legal advice than this.
Oh come on, it's easy! "In my opinion as a lawyer, you should release radioactive bees into the refrigerators of your customers."
Now that's bad legal advice.
Re: Coding Cloud Heroku May Face Lawsuit Over Bait-and-Switch Claims
#53In MIT's Mathematics for Computer Scientists course (6.042), I remember learning from Tom Leighton that in certain cases randomly distributing jobs actually IS the optimal solution to load balancing. This technique was somehow associated with Akamai, Professor Leighton's company. Maybe I am misremembering...
I think you are supposed to take least busy of two random nodes.
Re: Coding Cloud Heroku May Face Lawsuit Over Bait-and-Switch Claims
#54TLDR: RapGenius (YCS11), in a painful attempt to remain relevant, decides to sue their web host for running their slow code slowly.
If you're going to tldr; an article you should really read it. Rap genius isn't suing. No one, in fact, is actually yet suing.
Re: Coding Cloud Heroku May Face Lawsuit Over Bait-and-Switch Claims
#55Earlier quoted context omitted.
Even people who have been somewhat screwed by this issue with Heroku tend to love Heroku; Salesforce could make this right with generous payouts to affected people and 2-6mo of engineering to offer a better load balancer as a service (Actually, I think I could build this as a third party provider, even) EA is basically a lost cause; their business model and culture is the problem. Having better sacks at Dachau wouldn…
Well that's what they should have done BEFORE the threat of class action lawsuit. It makes them look at a lot worse if it happens after. I'm pretty surprised they didn't offer refunds already. It was pretty clear they were asked for, and with no update by now, it's safe to say they were refused. That seems unreasonable to me. If you were in the position RapGenius, would you honestly not have expected a refund already…
I wonder what happened to Heroku. They used to be awesome. They still have elements of being awesome, but seem either resource constrained or self destructive. I find it hard to believe Salesforce wouldn't give them what they need to do things correctly -- ranging from "go multi-AWS Region or move off AWS" to building a decent load balancing system to handling this fiasco.
Re: Coding Cloud Heroku May Face Lawsuit Over Bait-and-Switch Claims
#56Only lawyers think it's a good idea to deploy lawyers into the routing mesh.
Re: Coding Cloud Heroku May Face Lawsuit Over Bait-and-Switch Claims
#57Earlier quoted context omitted.
Um, why? I was one of many plaintiffs in a class action lawsuit against EA (which was settled in our favor). That did not help EA's image at all :) It looks pretty bad when your customers complain about problems that are hidden by your own monitoring tools, and then you tell them to buy more crap to fix it! It's not a small amount either -- as mentioned the queuing time was larger than the request time. And on top of…
Even people who have been somewhat screwed by this issue with Heroku tend to love Heroku; Salesforce could make this right with generous payouts to affected people and 2-6mo of engineering to offer a better load balancer as a service (Actually, I think I could build this as a third party provider, even) EA is basically a lost cause; their business model and culture is the problem. Having better sacks at Dachau wouldn…
> Actually, I think I could build this as a third party provider, even
I dont use Heroku, but if you read Rap Genius' original paper discussing the queuing problem, they specifically stated that there is nothing that they can do about it.
Re: Coding Cloud Heroku May Face Lawsuit Over Bait-and-Switch Claims
#58TLDR: RapGenius (YCS11), in a painful attempt to remain relevant, decides to sue their web host for running their slow code slowly.
RapGenius just recently raised $15m from Andreessen Horowitz; they hardly need to make 'painful attempt[s] to remain relevant.'
And they're not even involved with this lawsuit.
Re: Coding Cloud Heroku May Face Lawsuit Over Bait-and-Switch Claims
#59Earlier quoted context omitted.
New Relic isn't Heroku's tool, man. It's like a car dealership selling you a Pioneer stereo.
It's certainly not a disinterested third party that Heroku knows nothing about: http://news.heroku.com/news_releases/heroku-and-new-relic-pa...
Agreed, but it's not the one true monitoring system. I happen to be biased and think it's pretty good, but it's not a first-party monitoring system that they swore on a bible was correct.
Re: Coding Cloud Heroku May Face Lawsuit Over Bait-and-Switch Claims
#60>Heroku declined our request for further comment. “Unfortunately, we can’t publicly comment on legal matters,” said spokeswoman Dana Oshiro in an email. “Heroku is committed to our customers’ success and focused on delivering the best possible product and experience. We’ll continue to update our customers via our blog.” I don't run a company, and I'm not responsible for maximizing return on my shareholders' investmen…
This is normal, once legal threats are issued "we can't comment on legal issues...but customers are #1...blah blah" is the standard answer.
A mea culpa right now might haunt you in the long term.