5 ms·

I don't get it, all of these things are simple to do in Java. Ugly, yes, but still simple.

seertaak 18y ago
In case you haven't noticed, for the last several years there has been a totally irrational and even juvenile trashing of java in favour of fine languages such as haskell, erlang, ruby, python, etc. I think it's a good thing: it reminds us that even in our corner of the woods, where reason is supposed to reign, we succumb to the most banal fashions. Hackers typically like to point out that "normal" people speak much nonsense and hold irrational views. In fact, the same is true for us. Well, except me, that is ;)
- Tichy 18y ago
  I've been a Java developer for years and I don't think its trashing is irrational. Once you have seen alternative ways of doing things, going back to Java is simply painful.
  - flashgordon 18y ago
    i think the same argument goes for other imperative/OO languages... its a pain going back to C++ once youve done python (or ruby or haskell or lisp)... even worse when you have no choice but to use it at work:(
    - Tichy 18y ago
      Actually going back to C++ even seemed painful when I still was a Java developer.
  - seertaak 18y ago
    [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.
  - calambrac 18y ago
    I agree. As a longtime Java developer myself, it is horrible. But it's horrible on its own merits; there's no reason to make things up about what it can and can't do in order to trash it.
deleted 18y ago
[deleted]

In case you haven't noticed, for the last several years there has been a totally irrational and even juvenile trashing of java in favour of fine languages such as haskell, erlang, ruby, python, etc. I think it's a good thing: it reminds us that even in our corner of the woods, where reason is supposed to reign, we succumb to the most banal fashions. Hackers typically like to point out that "normal" people speak much nonsense and hold irrational views. In fact, the same is true for us. Well, except me, that is ;)

Tichy 18y ago
I've been a Java developer for years and I don't think its trashing is irrational. Once you have seen alternative ways of doing things, going back to Java is simply painful.
- flashgordon 18y ago
  i think the same argument goes for other imperative/OO languages... its a pain going back to C++ once youve done python (or ruby or haskell or lisp)... even worse when you have no choice but to use it at work:(
  - Tichy 18y ago
    Actually going back to C++ even seemed painful when I still was a Java developer.
- seertaak 18y ago
  [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.
- calambrac 18y ago
  I agree. As a longtime Java developer myself, it is horrible. But it's horrible on its own merits; there's no reason to make things up about what it can and can't do in order to trash it.

deleted 18y ago

[deleted]