Robinhood trading site seizes up, customers miss stock rally
bloomberg.com
bloomberg.com
It is kinda like a bank rush, only really well heeled institutions can survive everyone and their mother jumping in the fray.
Now.. the common question is whether the company should have an infrastructure that can support its customer load at times like this.
Another thing to consider is that there are so many great alternatives to RH that were online, despite encountering similar load. If the whole stock trading network went down that would be a different conversation, but users of other platforms were able to trade, and thus RH not being able to provide the infrastructure to handle the load is a huge disservice to its customers.
Hard to take that reply seriously.
Perse probably didn't know it was a hoax.
That said I don’t have any idea about how Robinhood implements them.
https://www.google.com/amp/s/www.cnbc.com/amp/2015/11/18/why...
Lots of other exchanges still offer them https://www.cmegroup.com/confluence/plugins/servlet/mobile?c...
I’d be curious how brokerages actually implement stops on exchanges that don’t offer them natively because synthetic stops have notoriously bad edge cases.
Is this a case of people putting all their eggs in one basket? Does Robinhood have a "guaranteed" 99.9xxx% uptime guarantee?
Sucks for a lot of people who evidently are putting a lot of money in the market and couldn't do anything due to a technical issue.
Regardless: Robinhood is aimed at individual consumers, not sophisticated investors. It's not uncommon for prosumers to have several brokerages, but of course you're limited in the size of the moves you can make (probably not a bad thing for the median Robinhood user).
If you cared this much, you probably had IBKR.
I was wondering why mentions of Robinhood blew up yesterday:
I'm know it can be done in python, but its about curbing any potential for human errors. Interested in seeing the RCA for this.
Without a more rigorous set of criteria we are arguing opinion. While my opinion is the same on static types there are people with their own experience on the other side of the argument.
They too have lived it.
Also, if "rigorous, non-optional" is good, why would you want _Java_ and not, I dunno, Haskell or ML or some other powerful type system? Is there any evidence this bug would have been prevented in Java? If anything, Java is prime ground for the related YYYY vs yyyy formatter bug.
Not even that much of a couterpoint; if you want strict typing, you can do it in Erlang with pattern matching / guards and tagged tuples, and/or with Dialyzer and type annotations.
I said that at the end of my comment. But like you said, you have to opt-in to more rigorous checks instead of being forced to do them.