D vs. C#

[Antonio]

Unknown W. Brackets escribió:
> Antonio,
> 
> Even at Microsoft, I would hazard the guess that different people 
> implemented the .NET Framework classes than actually developed the CLR, 
> or even VB.NET, C#, J#, etc.  Each probably even had its own project 
> manager, but that's really a guess.
> 
> Microsoft has the resources to put into this, but D doesn't have it all 
> yet.  If you are comparing infrastructures, D will not win against C#. 
> It is true that it is not ready for that fight yet.
No, obiouslly I'm not comparing them.
Otherwise, people is producing heterogeneous small solutions:  Some
"guided" work (a "unique" guided work) must be interesting in a common
library production.

> 
> That said, comparing it to C/C++ is a much easier win for much the same 
> reasons.
> 
> Some programmers do not need the full class library written for them, 
> though.  If I need to parse xml, I'll either use a C library or write my 
> own (which I have done.)  You're very correct that D is not a RAD 
> language, and I don't think it's intended to be one.
> 
I agree... but I don't need a RAD, I need "hight abstraction" (unified 
vision of the system resources): D is promissing a lot... really 
promissing good levels of abstraction without performance losting. I 
should be really confortable changing C# by D.


> Over time, different class or library frameworks will emerge for D, and 
> one will become popular.  Since this has not yet happened, most people 
> are not interested in the obvious comparison you've made - rather, in 
> the comparison for the future.
> 
Actually I use Mango and PostgreSQL acces for a "small" solutions
(server side)... Mango support for servlets is really a pleasure... this 
is my example about standards... why not to grow to other "server side" 
common resources (i.e. Data Base access,...)


> 
> Just my opinion.
> 
> Also, I disagree with your comments on C#; I don't believe it was 
> designed as the way to access the framework.  In fact, I think .NET 
> smells much stronger of Visual Basic .NET than of C#.  But that's really 
> an opinion.
> 
> Further, C#'s syntax and features are actually represented in a standard 
> which would theoretically be framework agnostic, much like JavaScript. 
> AFAIK.

I'ts true, but I allways use de same example: .Net/Java Virtual Machine 
is to Machine the same than Framework is to de Operative System.
¿Who wants to program without S.O. support?

No one I know works with C# without framework (no one I know :-/ )

> 
> -[Unknown]
>