Automated trading with R on IB

Enough of this nonsense. IBrokers cannot be trusted for live trade management. Maybe it’s ok just to pull data from IB API, but no serious retail trader automates with this shit.
Can you share your personal experiences which led you to this conclusion? I would be interested to learn what the limitations are.
 
Can you share your personal experiences which led you to this conclusion? I would be interested to learn what the limitations are.

If you are interested in automated trading, you can also the try the Python IBridgePy API. Let me know if you have any issues either using R API or the Python API. I will be able to assist you. Cheers!
 
Can you share your personal experiences which led you to this conclusion? I would be interested to learn what the limitations are.
What do you mean? How can I experience something that's not possible? It can't handle professional data feeds. You want to micro trade against the best of the best, using IB data and unstable front ends? Just donate your money to UNICEF. Every child deserves a chance.

This software is in no way affiliated, endorsed, or approved by Interactive Brokers or any of its affiliates. It comes with absolutely no warranty and should not be used in actual trading unless the user can read and understand the source.

"IBrokers is a pure R implementation of the TWS API. At present it is only able pull data from the Interactive Brokers servers via the TWS. Future additions will include more API access, including live order handling, and better management across R sessions."
 
  • Like
Reactions: 312
What do you mean? How can I experience something that's not possible? It can't handle professional data feeds. You want to micro trade against the best of the best, using IB data and unstable front ends? Just donate your money to UNICEF. Every child deserves a chance.

This software is in no way affiliated, endorsed, or approved by Interactive Brokers or any of its affiliates. It comes with absolutely no warranty and should not be used in actual trading unless the user can read and understand the source.

"IBrokers is a pure R implementation of the TWS API. At present it is only able pull data from the Interactive Brokers servers via the TWS. Future additions will include more API access, including live order handling, and better management across R sessions."

But what about Jeff? He's a good guy. Jeff wouldn't lie to us... :(
 
Thanks truetype I just connected with him on Linkdin, will send him a message and if my schedule permits I'll visit him in Chicago, only 6 hour drive for me (Toronto).
Why drive 6 hours to see this clown? Sounds like a smart guy, but I doubt you'll learn anything beyond what's already been described in the docs.
 
  • Like
Reactions: 312
Next time Burton Malkiel tells me "there is no free lunch in markets" I'm just gonna point him to this thread
 
Look at the dates from the posts of said forums. The IBKR Python API is fairly recent, I don't think it's been around longer than a couple years. You won't find many people using IBPy after it was released. IBPy is deprecated because there's simply zero reason to use it when you can use the API from the vendor and you're setting yourself up for a myriad of issues going forward.

It's nonsense to tell the OP to use a no longer supported, unofficial wrapper when there's an open source version provided by IBKR. You've been using IBPy for a while so for you the cost of switching is larger, but someone just starting should go straight to the Python API and forget about IBPy altogether.

You're pulling the usual crap found on ET and other forums. Assume I've said something I never did and then argue the imagined statement - I never said to use IbPy.
YOU
said that IbPy is a "shitshow", which is strong statement and then you didn't back it up with anything. "Shitshow" implies it's completely useless and barely usable while in real trading today, it works great.

IbPy is open source, you're free to edit it as you please. You can accommodate any changes IB does. The argument that when it changes something it's "broken" is false.

You're probably just very young, that's why you come around with parabolic statements without much thought put into them.
 
Take a small break here from the pros and cons of using IB's API implementations or not to learn WHY you've still gots sum [sic] problems Willis:

The bugs in programming are mostly due to using mutable data structures in the common programming languages. The incessant testing models going on today manifest themselves from this fact. You'll see more languages adopting them in the future. It's the only sane way out of the complexity involved with multiple threads trying to change shared state.

Rich Hickey's videos on YouTube from 2011-2012 are what you want to watch to learn why the current software practice of rampant mutability in software is messed up. You will have so much fun using immutable data structures (producing far less buggy or code or more easy to fix) that you'll never go back unless you absolutely have to to get some mundane things done within a GUI.
 
You're probably just very young, that's why you come around with parabolic statements without much thought put into them.

I am indeed very young. You'd be amazed what HGH and viagra can do for a man. Anyway, go back to day trading USDEUR in the Philippines... with IBPy. Feel free to trade in Assembler for all I care, it's your money.

And thank you for gracing us mortals with the bastion of experience that showcase your well-thought out, rich posts. You're the Stephen Hawking of amateur hour finance.
 
Last edited:
Back
Top