[Nitpick: it's "its", not "it's", because you're not abbreviating "it is".] Well, I beg to differ. Right tool for the job is the way I think of these things. J

[Nitpick: it's "its", not "it's", because you're not abbreviating "it is".] Well, I beg to differ. Right tool for the job is the way I think of these things. Java is the right tool for many jobs. Not for everything, but for many things. For our application (equity stat arb trading), java is certainly a good choice. Ease of network programming, serialization for free, lots of libraries available, good performance, excellent IDEs, good support for multithreaded programming; these are some of the attributes which make java attractive for us. One example where it's not the right tool was where we wanted to be able to evaluate moments of well-defined statistical processes. There was a lot of symbolic processing, so we used Scala for that part. Another example is scripting type stuff, we want to amalgamate lots of Java code and run stuff in an interactive environment. For this purpose, we chose jython. Use the right tool for the job.