This is why you don't fuck around with PR issues. They can easily turn into lawsuits.
Heroku Class Action
21–30 of 78 posts
Re: Heroku Class Action
#22Dear Heroku, slice off a piece of your offering that shows some love to the Ruby community again. Lets call it the Maple stack. Have this stack use the old routing infrastructure. Edit: To be clear, I do not support this legal action. I do want Heroku to hear the community, but I don't want it to go this far.
The old bamboo stack has the same old intelligent routing, but the intelligence is only within each router. When the number of routers increased, the intelligence stopped mattering because concurrent requests were highly likely to not be handled by the same router, making the routing effectively random instead of intelligent.
So what you suggest would be great, but unfortunately not possible.
Re: Heroku Class Action
#23oh look, a parasitic lawyer-company trying to suck some money out of a technology company. it must be a day that ends in -y.
You honestly don't believe that, if the allegations are true, Heroku has done something wrong?
I'd rather see everyone move away from Heroku than waste everyones time and money on the legal system, personally. The only ones who would win in a business class joint suit case would be the lawyers on both sides.
Re: Heroku Class Action
#24oh look, a parasitic lawyer-company trying to suck some money out of a technology company. it must be a day that ends in -y.
You honestly don't believe that, if the allegations are true, Heroku has done something wrong?
I don't think a class action lawsuit will right Heroku's wrongs, considering that most of the money ends up going to lawyers.
Re: Heroku Class Action
#25My startup is heavily invested in and tied to Heroku. We don't have the resources right now to get off of the platform quickly, but plan to as soon as possible.
Like Rapleaf, we have spent an enormous amount of effort optimizing and searching for the causes of latency, and overpay for dynos to reduce but not eliminate the chance of latency issues. Heroku has always told us it's our fault.
While I have no interest in recovering money through a class action lawsuit - which is just grossly unproductive - my confidence in heroku has been shattered and I am embarrassed to have chosen and advocated for them for so long. I look forward to getting off their platform for good, and there is no way I could recommend it to others for similar applications.
Heroku's most recent statement does nothing to resolve the issue for most of their customers, and does not reduce what is clearly a gross overpricing and misrepresentation of what they provide.
It's quite clear that Heroku is not just a bad, but a horrible choice for rails applications that are not carefully designed for concurrency and don't go against Heroku recommendations and use a concurrent application server.
Re: Heroku Class Action
#26Dear Heroku, slice off a piece of your offering that shows some love to the Ruby community again. Lets call it the Maple stack. Have this stack use the old routing infrastructure. Edit: To be clear, I do not support this legal action. I do want Heroku to hear the community, but I don't want it to go this far.
The old bamboo stack has the same old intelligent routing, but the intelligence is only within each router. When the number of routers increased, the intelligence stopped mattering because concurrent requests were highly likely to not be handled by the same router, making the routing effectively random instead of intelligent. So what you suggest would be great, but unfortunately not possible.
I'll just repeat my previous comment: For $60,000 per month they can't create a mode where all your dynos are behind a single HAProxy with "intelligent" least-connections load balancing?
Re: Heroku Class Action
#27My startup is heavily invested in and tied to Heroku. We don't have the resources right now to get off of the platform quickly, but plan to as soon as possible. Like Rapleaf, we have spent an enormous amount of effort optimizing and searching for the causes of latency, and overpay for dynos to reduce but not eliminate the chance of latency issues. Heroku has always told us it's our fault. While I have no interest in…
[deleted]
Re: Heroku Class Action
#28Can we please get this site hosted on Heroku for the irony?
Re: Heroku Class Action
#29Ok this is going too far. Did Heroku make a mistake? Yes. Did they mislead and lie to their customers? Yes. But is it worth pursuing a class action lawsuit that could ultimately ruin them - if not financially, but force their mgmt team to focus on this damn suit rather than fixing the damn problems? Hells no.
I hope RapGenius is not the lead plaintiff in this, otherwise I will be very disappointed.
I applaud them for raising this issue, and doing all the research they did. We are all much better off for it.
I applaud them for sticking to their guns to make sure Heroku fixes the issue.
But if they join this class action suit, in my humble opinion, it is one step too far. What is the max they can realistically expect to get back from Heroku? $250K? $500K? Surely not the entire $20K/mo, so I doubt it will be that much.
Given all the money they have raised so far, if I were one of their investors I would start to ask questions about if they are wasting their time frivolously beating a dead horse.
This is getting into 'bad karma' territory. I am sure someone, at some point, will want to sue RapGenius....they may remember how they behave now.
So yes, keep up the pressure, and keep forcing Heroku to fix their faulty systems.
But a class action suit dawg? I think not.
Re: Heroku Class Action
#30[deleted]