Differences between J# and C#

Hi
A lot of people ask me why I use C# instead of J#.

Can anyone tell me the differences, advantages and disavtanges comparing the two.

I'd like a resume and not links that I have to read tons of pages to find out. Of course, links to details are welcome, but only after a resume.

I think 500 ponts is worth the effort.

Thanks.
mak730Asked:
Who is Participating?
 
gregoryyoungConnect With a Mentor Commented:
btw: everytime you call a framework object in J# you are calling a C# object :)
0
 
farsightCommented:
resume ???
Do you mean "summary"?
0
 
mak730Author Commented:
ups. Yes, sorry for my bad english
0
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

 
gregoryyoungCommented:
1) J# is not yet supported by the .Net Compact Framework
2) J# is intended to provide Java compatability with .NET i.e. it is an easy stepping stone for current java developers
3) C# has a TON more documentation/examples around
4) J#'s runtime libraries will remain frozen at the JDK 1.1.4 level
5) J# code cannot define new .Net properties, events, value types, or delegates. this is HUGE


great quote ... "For .Net development, J#'s primary audience is hard-core Java coders who must target .Net, but who would rather live with J#'s limitations than switch to the more expressive and accommodating C#. "
0
 
gregoryyoungCommented:
#5 is a BIGGIE ...

you will see on almost every MSDN help page ...

you can handle the events defined by a class, but you cannot define your own
0
 
gregoryyoungCommented:
apparently #5 has been changed.

here are some other things though


The following features, which may be supported by other languages targeting the .NET Framework common language runtime, are not supported in Visual J#:

Operator overloading and the .NET Framework semantics associated with operator overloading.
Implicit and explicit conversions between types using the op_Implicit and op_Explicit conversion operators.
Support for defining the following .NET Framework constructs:
Value types
Custom attributes
Enumerations
Seamless coercion between Java-language data types and .NET Framework data types.
Compiler checking for CLS compliance (CLSCompliantAttribute Class)
If a single type implements two interfaces that each require the definition of a method of the same name and signature, Visual J# does not consider these methods distinct and needing different implementations. Visual J# only supports a single code body to implement all interface methods of the same name and signature.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_vjsharp/html/vjgrfjavacallingcom.asp is also worth a look at

0
 
mak730Author Commented:
ok, points are yours, just one more question: J# can use C# classes and components to create Web Apps?
0
 
gregoryyoungCommented:
yes but at that point why use j# :) ... imho if you want to use java go java, if you want to use .net go C#
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.