The poll does not ask the same question as the subject. My answer is Yes for the poll, but No for the subject. I'd probably prefer a closer-to-native* TWS, but don't think they should do it.
crusher said:
- May be an increased cost for IB
Maybe is a grave understatement. It's a huge amount of work, at a time when they have a full plate.
Personally, I prefer the "feel" and appearance of well-designed apps crafted with the native Windows UI controls to some of the Java/Swing/whatever counterparts**. Platform independence means nothing to me, nor, I suspect, to the vast majority of IB users and volume.
If they
did have to maintain platform independence (or at least Linux/Solaris/Windows/Mac), it would be a huge amount of work to develop natively for each platform without resorting to some sort of plaform-independent library, like Java
Might it be faster? I don't know. Most of TWS seems reasonable in performance for its capability, with the obvious exception of the charts.
I don't remember if the back-end was ever changed from pre-TWS4 (pre-Java) days. I know there was a long time when you could use the old (non-Java) app as well as TWS4. I seem to remember the back-end was some sort of C/UNIX environment. Maybe one of the IB software folks can comment?
*"closer-to-native": Almost everything anyone develops sits on top of some kind of framework or other set of libs. MFC, for example, while extremely useful, blurs the line between interpreted and compiled because of how generic some of the classes are, and how "interpretive" of runtime-specified params the underlying code has to be. Not that I don't use it alot, but you have to be careful in places where performance matters.
**A good example is the TWS grid. When you attempt to re-size a column by dragging the border, if the adjacent column responds to a click event (like the "Last Change/%" column), after dragging in that direction by a few pixels, the column stops resizing, and the clickable column gets a click event (and does whatever it's supposed to do with it). I'm under the impression that this is not fixable by the application programmer (at least not without some sort of hack).