Hello, As a potential new D user (just discovered this language 1 week ago), I can tell the following: 1. It is very likely that the first idea about D will be obtained from the wikipedia rather that the D website. 2. Someone that passed over this first step, will soon be confused by the D2 vs D1 and phobos vs tango debate. 3. Someone that will pass over the second step will be even more confused discovering that the dsource website linked from the main D programming website is obsolete (seems most projects are moving to github) and there is no up2date list of projects using D2.
I'm not sure about the point 3 but that is where I am after one week. If you look at this page http://www.d-programming-language.org/future.html, it talks about future post 1.0 plans. Is this the version 1.0 of D2.0? I think you should have a page describing the history of D to clear out the confusion. no need to answer my email, better fix the website in the same time. mache On Fri, Nov 18, 2011 at 6:00 PM, Paulo Pinto <pj...@progtools.org> wrote: > Am 18.11.2011 17:12, schrieb Nick Sabalausky: >> >> "Nick Sabalausky"<a@a.a> wrote in message >> news:ja6042$230j$1...@digitalmars.com... >>> >>> "Paulo Pinto"<pj...@progtools.org> wrote in message >>> news:ja3bcp$ied$1...@digitalmars.com... >>>> >>>> Hi, >>>> >>>> the only issue with your sentence is that the "efficiency of native >>>> code" >>>> is also >>>> possible with C#. >>>> >>> >>> I used to do a fair amount of C# and...no, it isn't ;) At least not >>> without a world of hurt. For example, try to read in a block of data and >>> impose a structure over it without any unnecessary copying or processing >>> and you'll see what I mean. >> >> It's better than Java though: At least C# actually *has* pointers. >> >> > > Sure, but I don't remember the last time I really needed to use pointers. > > Don't understand me wrong, it is good to have pointers around for the few > cases one might need them. >