: "Joseph T. Adams" wrote
: > However, VB.NET will be *much* closer to Java in terms of capabilities
: > and design patterns. I agree with the poster who indicated it might
: > be a good idea to wait for it if possible.
: However, because C# and Java both are "C-like" in heritage, wouldn't C# be a
: better candidate for a Java port than VB.NET?
VB.NET and C# are so similar in terms of functionality that they're
almost a wash. C# is superficially much more similar to Java, so it
certainly would be an acceptable choice.
However, if it were me, I'd still lean toward VB.NET, because it is
essentially the fusion of many of the best parts of VB and Java, and
should be easy to learn for both VB and Java developers, while C# will
seem odd for anyone without a Java or C++ background. I also believe
it will be more popular and better supported for the same reason.
Joe