Yeah, Visual C++ was always slow.
I don't remember all the details, but I guess to have half working STL support too them roughly ten years.

So online votes can be bought?
Offline votes can't?

Well, if I was not on an iPad I simply would copy paste your rant and exchange every NOT for a yes and every "C can", with a "C can't" etc. p.p.

If you really believe the **** you just wrote there, you don't qualify for discussions about software development etc.

I only agree that Java is bloated, because the need of writing 'public' in front of every class and method and 'private' in from of every attribute is indeed a waste of time, and it is ugly to read.

The rest of your post, especially the claims about how incompetent Java Developers are, how slow Java is, how resource hungry Java is ... simply shows you have no clue yourself about Java.

Hint: did you ever compare a 'real world' Java program in speed and resource consumption with an equivalent real world C/C++ program? Likely not. Why not? Because a Java program where 7 developers work 5 years on costs roughly 4.5million Euros. I doubt there is anyone going to invest another 10(?) million or regardless how much to craft an equivalent C program just to prove you can save a megabyte here and there and gain a few computing cycles here and there.

Guess what, my last 'BIG IRON' Java contract involved a SUN 'mainframe' with 1 terra byte of RAM. It had about 50 Java VMs running with max memory sizes between 2 and 16GB. The self made software running on it was worth roughly 100million Euros, likely more, I joined late in the project, no idea how long it actually ran. And guess what all the VMs where doing all the time? Idling, waiting for DB requests or Network requests to finish. Do you really think C programs ... or Erlang, or just insert your language of choice: would idle less? Would need less RAM? Would be cheaper to develop? (Programming DB access in C ... that is worth than the death penalty ... oh my)

Sorry, you can say about Java what you want. But if we had not Java, many big companies in our times would not even exist.

ROFL.
So, you claim to know the difference between an 'inspection' and a 'walk through' but actually don't know it?

And since when may the reviewers not have access to the VCS of the developers, regardless what kind of review style you chose?

Sorry ... perhaps you should not only read the books your favorite professor suggests but also some others?

There is no such thing as 'the right way doing code reviews' ... there are dozens of approaches, I mentioned two general categories above.

I'm not yelling at other users, why should I?
They don't listen anyway.
Sorry, did again not get your point, must be an english / german language barrier thing.
I assume you had a point to make?

You are wrong, he explicitly claimed he has an Eclipse (IDE) project, that can not be build from the command line. That is impossible!

He/she doesn't have to say anything like that. Said person is giving you a counter-argument to your claim that every IDE does such and such. I can also give you another example IDE that is not MS and
He did not give a counter example. He made a claim.
necessarily put things in text files: Oracle's JDeveloper I used JDeveloper ... and all I worked on was in text files ... care to point out, what is not?

Not all tools are IDEs. The OP is referring to tools that generate heaps of stuff (auto-gen code, property files, xml descriptors and what not) and that there are developers who do not know how all of that is supposed to work. You see that a lot in Java and MS land.
Tools are used to tackle a certain technology. The xml files, property files etc. etc. are not there because of the tool. They are there because the technology requires them. So if your co workers or employees can mot master the technology without tools obscuring them, then that is certainly not the tools fault, regardless what tool is involved.

The next tool you want to abolish is a C compiler, because no one using it knows anymore how to code in assembler?

Sorry, the talk WAS about IDEs as any other tool.

And perhaps you should read up what a 'straw,an fallacy' actually is instead of throwing it randomly into discussions.

So, again: what exactly does JDeveloper not store in a text file? What exactly prevents you building a project from the command line by issuing the relevant 'javac' and 'jar' commands?

Sorry, but your claim that you can not build a Java project that originated in Eclipse, without having the same layout is not only nonsense it is bullshit.

First of all I assume you mean directory layout _above_ package level?

Then please explain me why a command line like: javac -sourcepath YOURSOURCE:FOLDERS:HERE -classpath JAR:FILES:AND:CLASSDIRECTORIES:HERE does not work on your system!

I'm ignorant about MS.
Not about the topic, none of the GPs or the original poster ever mentioned MS.
But if programming means for you to work with MS technologies (erm, can you name that technology?) then ... hm ... I pity you.

Well, there are other options:
o pick a different customer
o pick different vendors
o educate your customer

That "real world" thing would not exist if you would stop supporting it.

Aikidoka are usually not angry, at least I don't know any who is :)

What was the point you are arguing about?

Oh, tools are bad, yes ... it is never the user of a tool, is it?

Sorry, that is nonsense.

All java sources in an Eclipse project are simply in one or more trees of directories.

If you can not cope with them without Eclipse then check them out of your VCS and use what ever editor you want.
And bottom line I really wonder when you do intensive code reviews: why dob't you utilize tools like gerrit or fisheye for it .... eeeek, another tool!

Oh, you do generate code with Eclipse or tools used by it? Perhaps you should then drop your academic attitude of 'not putting generated code' into version control?

Do you have a build system that can build your project from the command line? No? Why not? How do you even know that the security audits of the code you audit actually cover the code soon to be in production?

So now you blame Eclipse ... it is just a tool! And a fool with a tool is still a fool!

If blame an IDE for deficiencies in your software or software development process ... then there is something wrong with your approach, seriously!

Erm, if you want to point out that MS IDEs don't put stuff you work with into files, then say so. And if you are at it, explain where they put the stuff you enter (and if you know why, then point that out, too). Sorry, where else than in files should MS visual studio puts its sources?

If we have X, and something is an(one) order of magnitude bigger than X, then it is 10x bigger than X.
If it is 100x bigger than X then this is two orders of magnitude and if we are talking about 1000x smaller or bigger, as in this case: it is three orders of magnitudes.

Nope, I don't work with Microsoft Technologies.
In 1997 a company I owned partly was so smart to use VisualSourceSafe as VCS (considering that it did not really work, I can not get why they did it).
Instead of having files versioned in files they used like SVN the database approach. And yes they had back ups.
When the VSS DB got corrupted, all work of two years of about five developers got lost. Well, mine was additionally in my private (back uped) RCS ...
Due to licensing issues it took them months to get the backups back into a working VSS ...
That was the last company I worked with MS 'tools' /languages for coding 'real' software.

If your environment demands to use particular tools because vi and text files are not enough, then something is seriously wrong. And I doubt that absolvents from universities that only can use MS tools and can only work in MS ecospheres save so much money in the long run that it is worth it.