C# or C++ Advantages over Java

[complete]

What advantages -- if any -- does C# have over Java?
What advantages -- if any -- does C++ have over Java?

[DJMaze]

C++: Speed, loads of speed.

Don't compare Zend vs C++ because the Zend software has Java "built-in", any application you create depends on the JRE which is slow as hell.

There are benefits in Java, but you didn't ask that.

C# sucks in my opinion because it is M$ and it is RAD and due to that, hard to code to your hand if you need modifications.

[toe_cutter]

This is really a tough subject because what someone considers an advantage someone else might not.

I can tell you what Java does not have that C++ does.

• No global variables
• No pointers
• No support for mulitple inheritence
• No support for templates
• Cannot overload operators
• No preprocessor

Now like I said some people may thinks these are disadvantages and others advantages. For me C++ gives you enough rope to hang yourself if your not careful, and Java gives you less rope.

TC

[AssKoala]

Originally Posted by DJMaze

C++: Speed, loads of speed.

Not always the case. In many cases, the speed differences between C#, C++, and Java are nominal. I/O operations will take the same time whether they are called from a C program or a Java program, for example.

Originally Posted by complete

What advantages -- if any -- does C# have over Java?

Broad, but the langauges are similar enough to make an overview doable.

Advantages:
- C# executes significantly faster.
- C# gives you closer access to DirectX.
- Use of C# allows you to use other .NET enabled langauges interchangeably in your code.
- Interoperability with C++ and other languages
- C# is an open standard, Java isn't. I don't care about this one, but most people who say dumb things like "C# is M$" have no idea what they're talking about seeing as C# and the associated Intermediate Languages are completely open while Java is 100% controlled by Sun.
- Platform Independence.
- Many more. Try out google.

Disadvantages:
- While C# is platform independent, the .NET implementation of the MSIL is not.
- Java has a longer history (e.g. more libraries are around for Java)
- Java's containers don't suck ass

Originally Posted by complete

What advantages -- if any -- does C++ have over Java?

Too broad of a question to answer in a webforum. Use google. I'll get you started.

[Valmont]

Don't think in terms of advantages, think in terms of needs or requirements. If this is setup properly, the right tool for the right job wil emerge.

[kyoryu]

Originally Posted by AssKoala

Disadvantages:
- While C# is platform independent, the .NET implementation of the MSIL is not.

But, there is an open-source version available. It's not at 2.0 yet, though.

Originally Posted by AssKoala

- Java has a longer history (e.g. more libraries are around for Java)

How's the interop between Java and c/c++ (native) libraries? I know C# is getting better - there may not be as many native libraries, but it's pretty easy to hit native C++ libs from C#.

Originally Posted by AssKoala

- Java's containers don't suck ass

C# containers don't suck ass in .NET 2.0. They did prior to that, though.

Valmont is right, though - think in terms of requirements for the job at hand. There's no "best" tool, only the best tool for the job you're trying to do.

[AssKoala]

Originally Posted by kyoryu

But, there is an open-source version available. It's not at 2.0 yet, though.

Yeah, but it isn't stable enough. I mean, I'm on the side of the fence that says .NET on non-Windows = unstable = nono.

Originally Posted by kyoryu

How's the interop between Java and c/c++ (native) libraries? I know C# is getting better - there may not be as many native libraries, but it's pretty easy to hit native C++ libs from C#.

Well, you can interop in any .NET language (some things may need to be wrapped in C#), but Java is nowhere near the interoperability of .NET.

Originally Posted by kyoryu

C# containers don't suck ass in .NET 2.0. They did prior to that, though.

Yeah, that is true, but a lot of people aren't writing their apps in .NET 2.0 yet.

Originally Posted by kyoryu

Valmont is right, though - think in terms of requirements for the job at hand. There's no "best" tool, only the best tool for the job you're trying to do.

Aye, most def.