When would you not use java

Question

This is a discussion I would really like to hear some other opinions about. I know some people who keep thinking Java sucks and when they try to use it, they use it for completely the wrong tasks. Now I was thinking, in what situations should you avoid it altogether? This could become a nice reference thread to point those idiots to :)
I would avoid Java for:
- performance critical solutions (perfect timing, per frame graphics analyzers, etc.)
- general public applications. You have to install java first to run your software, which a lot of users will screw up or simply won't do. Java also eats up a lot of memory.
- platform dependend problems. Generally if your problem description includes the word "Microsoft", you should NOT use Java to try and fix it. You should be using Visual Basic or C#.
These are really common examples that I see on this forum almost every day. Are there any other examples that are worth mentioning?

Answer 1

Q>>Now I was thinking, in what situations should you avoid it altogether?
A>>When they use it for completely the wrong tasks.
You answered your own question.
I would avoid Java for:The stuff you say you would avoid java for, pretty much , well to me, says you won't use java.
- performance critical solutions (perfect timing, per frame graphics analyzers, etc.)Why not, all depends on your algorithms.
- general public applications. You have to install java first to run your software, which a lot of users will screw up or simply won't do. Latest Linux Distros, like JDS, come already packaged with JRE, so this isn't 100% true.
Java also eats up a lot of memory. So does windoz OS. I guess I'll avoid it.
- platform dependend problems. How so??? again see your original Question (Q above).
Java was created for platform independance.
When you create a program that considers Solaris, Linux, and cough windoz, Oh , don't forget MAC, you program each case, no big deal.