What do Java programmers feel is missing from C#?

I may be opening a can of worms and don't want to start a religious war,
but...

What features of Java do Java programmers miss when working in C#?

Other than, of course, great portability.  C# has more limited
cross-platform portability (Mono).

I'm thinking more about data structures and ways to express algorithms.

mc wrote:
> I may be opening a can of worms and don't want to start a religious war,
> but...
>
> What features of Java do Java programmers miss when working in C#?
>
> Other than, of course, great portability.  C# has more limited
> cross-platform portability (Mono).
>
> I'm thinking more about data structures and ways to express algorithms.

I sort of liked fall-thru in switch statements, but I'm the first to
admit that it can lead to unreadable code.

The Java Language Reference mentions something called a Duff's Device,
which I never really understood and which C# would probably frown on
anyway.  :)

dleifker

"Dan Leifker" <dleifker@leifker.com> wrote in message
 news:KIWdnbA267Pogk7anZ2dnUVZ_iydnZ2d@co
mcast.com...
> mc wrote: 
>
> I sort of liked fall-thru in switch statements, but I'm the first to admit
> that it can lead to unreadable code.

Actually, I think the switch statement is the most awkward thing in C#,
largely because it isn't the Fortran-like thing from C that it looks like.
I wish C# had adopted the Pascal case statement.

mc wrote:
> I may be opening a can of worms and don't want to start a religious war,
> but...
>
> What features of Java do Java programmers miss when working in C#?
>
> Other than, of course, great portability.  C# has more limited
> cross-platform portability (Mono).
>
> I'm thinking more about data structures and ways to express algorithms.
>
I am just esthetically prefer Java. I think Java is simpler language.
There is no properties, no defined operators, no delegates - for me it
makes everything more clear. I know only one language that is comparable
in transparency - C.
I also liked Java collections Api and general API more - just preference.
Java has checked exceptions and this makes dealing with exceptions more
easy - you mostly know which exceptions you can expect.
JavaDoc - is more clear that C# XML Docs, and in my opinion leads to
better quality API descriptions.
I prefer Java Strict package / folder structure to unclear C# conventions.

mc wrote:
> Actually, I think the switch statement is the most awkward thing in C#,
> largely because it isn't the Fortran-like thing from C that it looks like.
> I wish C# had adopted the Pascal case statement.

But I seem to recall (good grief, I learned Pascal in 1981) that the
Pascal case statement had no default/otherwise/else, right?  Well, I
don't think it did on that creaking Univac we used, but I just Googled
it and and I guess other flavors of Pascal did support it.

See also Brian Kernighan's famous paper about Pascal at:

http://www.cs.virginia.edu/~evans/c...-on-pascal.html

One bit of trivia about the Java default (I think) is that it can occur
anywhere in the case sequence, even at the top.

cheers
dleifker

>> I wish C# had adopted the Pascal case statement.
>
> But I seem to recall (good grief, I learned Pascal in 1981) that the
> Pascal case statement had no default/otherwise/else, right?  Well, I don't
> think it did on that creaking Univac we used, but I just Googled it and
> and I guess other flavors of Pascal did support it.

Yes... when I say Pascal I really mean Turbo Pascal and Delphi.  Early
Pascal was impoverished in some ways, as Kernighan pointed out in the paper
you cite.

> http://www.cs.virginia.edu/~evans/c...-on-pascal.html

Well now that just has to be the IDE...  Visual Studio is just so 1990's



"mc" <look@www.ai.uga.edu.for.address> wrote in message
news:4fyAj.4184$by3.1171@bignews5.bellsouth.net...
>I may be opening a can of worms and don't want to start a religious war,
>but...
>
> What features of Java do Java programmers miss when working in C#?
>
> Other than, of course, great portability.  C# has more limited
> cross-platform portability (Mono).
>
> I'm thinking more about data structures and ways to express algorithms.
>
>

"Nobody" <nobody@shaw.ca> wrote in message
news:lyYAj.66457$pM4.24579@pd7urf1no...
> Well now that just has to be the IDE...  Visual Studio is just so 1990's

What kind of IDE do you prefer?


>
>
>
> "mc" <look@www.ai.uga.edu.for.address> wrote in message
> news:4fyAj.4184$by3.1171@bignews5.bellsouth.net... 
>
>

On Sat, 8 Mar 2008 10:26:56 -0500, "mc"
<look@www.ai.uga.edu.for.address> wrote:

>I may be opening a can of worms and don't want to start a religious war,
>but...
>
>What features of Java do Java programmers miss when working in C#?
>

I miss the slow performance of Java and overall lack of productivity
and the vast amount of crappy offshored leftover code I used to work
on.

I get so much more done in C# it leaves me longing for that crappy
Java environment I left behind.

Harry Walters wrote:
> I miss the slow performance of Java and overall lack of productivity
> and the vast amount of crappy offshored leftover code I used to work
> on.
>
> I get so much more done in C# it leaves me longing for that crappy
> Java environment I left behind.
I did a quick Google search for "java c# benchmark" (try it yourself)
and it seems that it's only that offshored code that is slow and crappy
and not Java itself, because all benchmarks I could find concludes that
Java is way faster than C#.