Java IDE's don't compete with Visual Studio

Um, excuse me sir but I call shenanigans on that. And unlike you, I actually have a source. Here is a list of the VS ReSharper plugin compared to plain VS: http://www.jetbrains.com/resharper/features/ComparisonMatrix_R4.html

Be aware that these are the features VS is missing that Intellij IDEA (a java IDE) comes with out of the box. And when you're done with that, you can head over to the Intellij IDEA feature list to see what it has over ReSharper: http://www.jetbrains.com/idea/features/index.html

Please, show me your list of what VS has over Intellij IDEA. I'll settle for what it has over Eclipse. I really, really, really want to see this list. I ask in every slashdot thread where someone gets modded up for comments like this.

PS: Yes, I'm aware these two tools are made by the same company.

...and as such, anything that would spoil a book/movie would spoil a game.

You need to get your priorities straight.

To me it makes a lot more sense to write 100% of your program in, say, Perl. (s/Perl/Python/g or s/Perl/Ruby/g is that's what turns your crank.) You pull in some CPAN libraries, many of which have the time-critical stuff written in C for good performance, but you don't have to touch the C. If there does turn out to be some very time-critical loop that you really want to optimize, and it's not something generic that's available in CPAN, then you write it in C and interface it to your Perl program. You end up writing 99.9% of your own code in a nice high-level language, and 0.1% in a crufty low-level language, and you get good performance.

How much slower is it going to be in Javascript? Is it so slow that the average linux user is going to notice? If not, I think you're preoptimizing.

FYI, Java has a JS interpreter called Rhino and it lets you compile the JS into .class files for performance improvements. You can read about it here: http://www.mozilla.org/rhino/jsc.html Perhaps the same could happen with these linux applications.

But, as was said in that interview, the problem is convincing the "Developer Managers". You end up competing with people who use the Bait and Switch technique: They claim they can produce code faster and cheaper than you, but really, it's unmaintainable. We need to convince our managers that by saying no, we're doing them a favor.