You mentioned "limitations we see in the Java-based TWS." Your
comments are about GUI programming in Java. I'm looking for problems
with the TWS Java API.
Is this what you are trying to say? "If you write a GUI trading
program in Java, it's going to suck in the same ways that TWS does."
If that's it, I'm not concerned, as the Java interface I'm planning
does not have a Java GUI.
toggle quoted message
Show quoted text
--- In twsapi@y..., "dtkamp" <dkamp@e...> wrote:
--- In twsapi@y..., "kgeis" <kgeis@y...> wrote:
Please comment on the Java limitations. I've heard nothing of the
sort except for performance issues from people who don't know what
they are talking about.
Hi Ken. Right, I would put performance issues at the bottom of the
list of limitations. This is a huge topic to start a discussion
about, but will outline a few points broadly. BTW, I don't have
anything against Java or the notion of Java, having worked with it
for a couple of years.
- Lots of bugs, which are very difficult to work around, often
leading to use of platform-specific native code or tweaking and
recompiling SUN's code that one shouldn't really be touching. (I
think our list at one point had grown to something like several
hundred Swing bugs that we had worked around or fixed, although they
have addressed many of these in later versions of Swing.)
- Unless your apps are fairly simple (which they may well be), the
Java UI classes suffer from their need to be cross-platform (i.e.,
they can't afford to take advantage of many platform-specific
features, and hide access to some of the most basic stuff).
- Most of the cool Java stuff is finding its way into
Microsoft's .NET. Microsoft (like it or not) devours everything in
its path. If we're not going to break up this monster, then we can at
least avoid getting stepped on it (kind of like trading amongst the
investing giants).
So unless one is really, really serious about cross-platform
development (Macs and Unix), I would personally be really, really
hesitant to use Java for a trading app.
