This post originated from an RSS feed registered with .NET Buzz by Sudhakar Sadasivuni. Original Post: Java has finally catch up with C# (?) Feed Title: {Sudhakar's .NET Dump Yard;} Feed URL: http://www.asp.net/err404.htm?aspxerrorpath=/ssadasivuni/rss.aspx Feed Description: using Sudhakar.Dotnet.Blog.Main; Latest .NET Buzz Posts Latest .NET Buzz Posts by Sudhakar Sadasivuni Latest Posts From {Sudhakar's .NET Dump Yard;}

A Slashdot post and my buddy Ivarturi's blog pointed me to this..

"if you're doing C# and your foundations in OOP are rock-solid, there really isn't any difference whether you're coding C# or Java."

The list of enhancements to Java

1. Generics (C# 2.0 already supports this)
2. Enhanced For-Loop (the foreach construct in C# 1.0, duh!)
3. Autoboxing/Unboxing (C# 1.0 already has this, everything is an object, even the primitives - not really, but they do it so well...)
4. Typesafe Enums (again C# 1.0 already implemented this, but I think they've added a little bit more twist in Java, that its actually a better implementation)
5. Varargs (C# 1.0's params construct, ellipsis construct in C++)
6. Static Import (I don't know if C# 1.0 has this, or C#2.0, but C# has a construct for aliasing your imports - which is way cooler. Static Import, actually promotes bad coding habits IMHO)
7. Metadata/Annotations (this is C# 1.0's Attributes, Sun's upturned noses just gave it a fancier name - also,
   C#'s implementation is better and more intuitive)

I found this comment very interesting

Cakoose :- "C# vs Java, mostly a tie (c# good: ref and out parameters, indexers, foreach; c# bad: properties, operator overloading)"