If you read what I actually said, I never laid claim to it running on ANY machine. But if you really want to develop on any machine then there are other IDEs that dont have memory issues, unlike your beloved Eclipse.
Any machine? Really?
But Eclipse DOES run on Java, and is a real world example of a Java Application. And given that there are plenty of other IDEs for various languages out there, theres plenty to compare it to. Visual Studio, Delphi, SharpDevelop, etc, all dont run on the Java VM and run pretty fast by comparison. So looking at it as a whole, given that ultimately they ar ALL mainly fancy text editors, its a fair observation to say that the Java VM is likely the cause of the speed and memory issues with Eclipse.
Eclipse is not affiliated with Java
You are correct however in saying I dont know a huge amount about the JVM Garbage collection. But then, if you need to learn that much about how it works, I'm sure most coders would rather handle the memory themselves, as the JVM isnt doing a great job.
On the whole i dont mind Java as a language- there are some silly things - like Mojo pointed out (no operator overloading, unless Sun think its OK and build it into the language?!) But the langauge is only as powerful as the VM it runs on. The JVM is in my experience slow and prone to crashing. If Java ran on a decent platform, I'm sure I'd take the time to re-evaluate the the entire thing, but as Java and the JVM are so interconnected its difficult to say "Java is great", because it's let down by its runtime.
Java became popular because it's a solid language
Visual Studio Express Editions are free if you want to use them. And given Mojo's original point about Eclipse i think it was fair to single it out.
Obviously you haven't done the slightest bit of research. All of the IDEs you mention are free. If you must pay for one, there are plenty of 3rd party commercial Java IDEs and other tools that you can choose from
In what way is editing a config file telling you how something works? But understanding XML has nothing to do with understanding development or coding (at least nt if your just editing a config file). If config files give you a hardon, then you can still edit them in a quality tool like Visual Studio, or you can go ahead and use the IDE. I still fail to see how understanding that [insert app name here] uses a config file and editing that directly has ANY bearing on how much you know about the app or even development. It does of course make you more prone to errors, as you could inadvertantly change a value to an unsupported value or change the value only to find its overridden in some other config file (you know, the kind of thing Oracle does), but never be any wiser that your oh so clever tinkering has achieved absolutely nothing, wheras letting an IDE do it will shield you from thse kinds of things.
Yeah, it's much better to let the GUI shield you from understanding how things work.
I'm sure there are some people out there who love advocating things liek this. But typically these are the sort of people who like to keep computing away from the masses - I'm not talking about development here. You'd rather everyone ran Linux, and couldnt install a simple aplication without phoning you up for help and getting on their knees to beg for the knowledge of how to simply open an executable jar file. On the other hand, I'd rather computing was made easier for the masses.
Speak for yourself. Don't assume just because you don't have the ability, that no one else does.
If you'd like to keep languages difficult, why dont we all go back to ASM? i used to code in ASM, C, C++, Delphi, and the point of each jump was to make my life easier. From the Eaier Syntax of C compared to ASM, to the OO paradigm of C++, to the (work related) jump to Delphi, and then to the speed and memory friendly virtues of C# and the .net platform. Now maybe if I'd tried Java before C#, I'd have a warm fuzzy feeling about it, but I didnt and I dont. It's got virtually zero features I'd like to go over to C# (checked exceptions might be good, but i think thats about it). Time passes and there arent a huge number of people still developing in asm, compared to 10 years ago. There are fewer C++ jobs out there. Developers like to migrate to languages and environments that do more for them, so they dont have to worry about solving the same problem time and time again. In 10 years, I'm sure you'll love solving the same old issues you had today (probably in a config file somewhere), and good for you, but open minded people (ie not Java developers, clearly) will have moved on and be working on the next computing paradigm, using tools that fit the job.
I probably dont have enough experience to evaluate Java. But when its easier to set up a low level language like ASM that gives you no help whatsoever in terms of libraries and so on, you know there is a serious problem. Maybe they are "newbie" issues. Maybe I just didnt care enough to find a way around them, because my 1st impression was this an elitist language that expects you to be an expert from day 1 - and this is clearly your opinion too! When I have made language jumps before there has always been a learning curve, but new java Developers are faced with Mt Everest, and a toothpick to help get up it.
All of the things you are mentioning are complete newbie issues. If you're that much of a beginner then you don't have enough experience to credibly evaluate Java.
Good luck to you. I choose not to use java anymore, but unfortunaletly sometime work commitments mean I have to, helping keep the fire of hatred alive.
Don't hate. Some of us make plenty of money doing what you and others like you cannot. Java isn't going away anytime soon. If you don't like it don't use it. Stick with Visual Basic