Is anyone woring VC++ and Java professionally?

[Masaaki Onishi]

Hi, all.

Two years ago, I have studying Java by myself in order to enhance my school

assigment, mainly applet. However, after this, I've come back VC++ again and I've never made Java code again.

Now, I made CSocket program to do another school assignment by VC++ and

try to make the same program by Java, JDK1.6, not MS J++.

As a result, I noticed how Java is suitable language to make Internet program.


But, I don't want to make windows programming by Java because my idea is that

VC++ is best to make window programming, not including Network program.

When I come back Java again, I try to focus only on making networking program by

Java. That is, I want to choose my language, VC++ or Java by target programming.


Does anyone have the same idea or I should focus on only one language?

When you are working the project by both VC++ and Java, please let us know

your idea.


Thank you in advance.

-Masaaki Onishi-

[Erik]

If you can write it in Visual C++ do so. If you are limited to time, write it in

Java, you will probably be able to write it a bit faster.

-Erik

[idfx]

I think it's mainly a performance issue. I have never seen a Java

program run as fast as a comparable VC++ program, I think mainly because

the VC++ compiler is older and more thoroughly optimized. I would almost

never use Java to try and write anything using 3D, for example, because it

would just execute too slowly. On the other hand, if it's a simple grep-

type operation through an online DB, Java could be ideal, because it's so

much easier to write, and your user will be expecting some degree of delay

anyway.

You could also, if you wanted, go the encapsulation route and write an

application in both languages, compiling components separately, which should

be transparent once compiled to native code, but that can get confusing, and

I don't recommend it. The exception is when you want to *reuse* a bunch of

code, which happens to be in one language or the other, in which case it's

usually more time-efficient to just use the old code than re-invent it.