<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/4.1.92">
</HEAD>
<BODY>
I think most of programmers has an analytical mind. So IMHO a comparison chart (with others programming languages) of features / benchmark / "how-tos" will work better than a page filled of words. <BR>
<BR>
Il giorno lun, 14/11/2011 alle 10.15 +0100, Timon Gehr ha scritto:
<BLOCKQUOTE TYPE=CITE>
<PRE>
On 11/14/2011 02:50 AM, Andrei Alexandrescu wrote:
> Walter and I have been working on the website for a while. We want to
> crystallize a clear message of what the D programming language is.
>
> Please take a look at <A HREF="http://d-programming-language.org/new/">http://d-programming-language.org/new/</A>. The work
> is content-only (no significant changes in style, though collapsible
> examples and twitter news are a new style element).
>
> Feedback is welcome.
>
>
> Thanks,
>
> Andrei
Looks good, I think this is the right direction.
Nitpicks:
1.
// Type deduction works for function results. This is important for generic
// functions, such as min below, which works correctly for all comparable
// types.
auto min(T1, T2)(T1 lhs, T2 rhs) {
return rhs < lhs ? rhs : lhs;
}
It does not. The two types need to have a common type as well.
2.
The scope statement example should actually show transactional code.
Otherwise the poor reader feels fooled into clicking "See example".
Using scope(exit) to write something at function exit is useful for
debugging, but scope(failure) is the real thing that is important to show.
3.
If contract inheritance is to be promoted on the front page (and it is
certainly something that may attract developers), it should actually work.
4.
If we can find a less buzzy word than 'Multi-paradigm power' to describe
D's multi-paradigm power, that would be nice, but I am also fine with
the current state of affairs.
5.
The most important language features are not displayed at all. Where are
Metaprogramming, CTFE and code generation? It sure is hard to come up
with a short but convincing example, but I think we should try to.
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>