Necessities for Adoption of D

Vladimir Panteleev thecybershadow at gmail.com
Sat Feb 9 20:59:03 PST 2008


On Sat, 09 Feb 2008 23:42:27 +0200, Hans W. Uhlig <huhlig at clickconsulting.com> wrote:

I'll reply to some points that haven't been replied to.

> 4) Write once, run everywhere. - This one may make me sound like a loon but Sun had the right idea. Just not the bast implementation. I will clarify however I said Write once, not compile once. Most system specific tasks for application level programming are handled by the standard library. This includes gui integration, simple and native cross compile tools and integrated tar/compression support.

About GUI integration - I don't think it should be the burden of the language to provide that. There are several binding libraries for cross-platform GUI libraries which work pretty well (an example: http://wxd.sourceforge.net/ )

> 5) A library packager - The scripting languages got it right with cpan, simple quick, easy, no complex installation instructions, just cpan install x. Being able to do this and keep your libraries up-to-date quickly and easily is a godsend to most programmers. DSource is nice, but it lacks a lot in usability, and being able to figure out core from cruft.

We have this with Gregor's excellent DSSS ( D Shared Source System, http://dsource.org/projects/dsss/ ).

-- 
Best regards,
 Vladimir                          mailto:thecybershadow at gmail.com



More information about the Digitalmars-d mailing list