D vs. C#

[David Brown]

On Sun, Oct 21, 2007 at 01:25:55AM +0200, Yigal Chripun wrote:

> 1) it's a poor imitation of Java. Java may have its cons but at least they 
> try to be consistent with the design of the language - every new feature 
> goes through a JSR. this may make the language to evolve in a slower rate 
> though. compare that to the MS approach of including the kitchen sink. the 
> language has many features meant for corner cases which makes it bloated.
> on the other hand other features were discarded like the covariance of 
> return types, which is heavily used in Java land.

C# fixes many problems with Java, at least in my opinion.  C# 2.0 adds
generics which cover many of the cases of templates.  It has full support
of the VM, so executes efficiently and safely.

> 2) who needs another proprietary language?? that's the most important issue 
> for me. the mono project is a VERY stupid idea. it's a lost cause and a 
> wasted effort - trying to play catch-up to MS while it constantly 
> introduces breaking changes to the spec.

C# is not proprietary.  It is an ECMA and ISO standard.  What makes mono
stupid?  I've done development under mono and found it to work quite well.

Where they play catchup is not the language but Microsoft's ever expanding
proprietary libraries.

A big advantage C# has over D is that it is a standard, and there are
multiple implementations.  It's tradeoff choices may not be appropriate for
all applications (using a VM most importantly).

I think for the most part, D is a better language.

David