A summary of D's design principles

[Jay Byrd]

On Sat, 18 Sep 2010 14:20:20 +1200, Nick B wrote:

> On 18/09/2010 12:28 a.m., Justin Johansson wrote:
>> On 17/09/2010 6:48 PM, Nick B wrote:
>>> On 16/09/2010 5:58 a.m., Andrei Alexandrescu wrote:
>>>> A coworker asked me where he could find a brief document of D's
>>>> design principles. This was after I'd mentioned the "no function
>>>> hijacking" stance.
>>>>
>>>>
>>> there is no one, true, only to be used, library. D supports diversity.
>>
>> Using Walter's words this is a "trite platitude".
>>
>> Comments such as these are akin to saying "D is carbon neutral" without
>> a supporting argument.
>>
>> Can you please support your argument with more substance, i.e. more
>> sausage and less sizzle. :-)
>>
>>
> Is the fact there are two libraries, and not one, or twenty, a strength,
> and not a weakness, of the language and the D community.
> 
> For example, see this list of (approx 100) C++ libraries:
> http://www.trumphurst.com/cpplibs1.html#9
> 
> I think that this large number of libraries, just leads to fragmentation
> of effort by the C++ community.
> 
> Nick B

I gather that you are quite new to programming. Check /usr/lib on any 
linux system -- or check CPAN. Libraries are rife, and for good reason. 
And this has nothing whatsoever to do with Phobos vs. Tango, which are 
far from the only libraries for D -- their significance is that they are 
*core* libraries, akin to libc in C.