C# vs Java Applet

Well, it depends on where you want the program to run. If you want the game to run in an internet browser, use a Jave Applet. If you want it as an exe, use C#.

Im not too fussed really however i was thinking more on the lines of which is the easier method

I would go with Java, because there are alot more resources and tutorials focused on Java than C#.

LOL thanks stompy. I was thinking the same as u initially but had started a game in C# and come to great difficulties in finding help online such as code to help build my game. I only got decent hits with c# when looking for collision detection but even that was 90% irrelivant. However when it comes to Java i could find everything i need.

Thanks for clearing it up for me matey

Also there's the bastard child of applets and applications, using Java Web Start. It gets rid of the nasty applet sand-box security and allows you have to have off-server dependencies, automatic updating, etc. All with the ease of launching from a browser just from clicking a link. JWS might not be supported by machines running earlier versions of Java, though.

wel i have come across coding which brings up messages such as deprecation.

Quote:

Original post by Optus Also there's the bastard child of applets and applications, using Java Web Start. It gets rid of the nasty applet sand-box security and allows you have to have off-server dependencies, automatic updating, etc. All with the ease of launching from a browser just from clicking a link. JWS might not be supported by machines running earlier versions of Java, though.

It's supported by pretty much every implementation out of the box, now (since 1.3 I think). If not, your user is probably running an older machine with Win9x and we want to try and discourage those people as much as possible [grin].

Applets are odd little things that aren't directly comparable to C# applications; compare C# applications to Java applications. Of course, you might find an applet easier to write and launch (via Java Web Start)...

The deprecation warnings are because the library has evolved, and old ways of doing things are no longer preferred. Recompile with --deprecation so you can see exactly what "deprecated API" calls it's complaining about, then go look up the complained-about classes and methods in the library javadoc to figure out how to fix them.