D vs Java

[pragma]

In article <dvhr8j$eg0$1 at digitaldaemon.com>, Hasan Aljudy says...
>
>Walter Bright wrote:
>> I'm no expert on Java programming, but I get this question a lot: "What 
>> compelling reason does D have that would entice a Java programmer to switch 
>> to D?"
>> 
>> I know several of you have come to D from Java, and are expert Java 
>> programmers, so you folks' reasons would be very valuable. 
>> 
>> 
>
>no VM!!
>
>If it wasn't for Java's VM, maybe I wouldn't have moved to D.
>
>Other reasons that maybe compelling for some:
>not restrictively OO (although in java you can work around it by 
>declaring static methods & variables all over the place)
>

I'll second that.  These are the core reasons for switching from Java to D, or
even .NET to D for that matter.  The rest is just icing on the cake.

On a less technical note, I have enjoyed the fact that "D is just D".  Its a
nice switch from the "Sun Java(tm)" branding that has been pasted on everything
Java from the very start.  When one uses Java, the branding is so overt that it
makes one feel like they're using someone else's tool, rather than one of their
own.  I honestly feel that its small touches like this that keep D near and dear
to our hearts.

- EricAnderton at yahoo