Andrei Alexandrescu:

> Guess we could link from dlang.org to some. -- Andrei

A simpler solution is to to just link to this page, that contains the links to all pages that contain D entries:

http://rosettacode.org/wiki/Category:D

Bye,
bearophile

On 4/24/14, 10:30 AM, bearophile wrote:
> Andrei Alexandrescu:
>
>> Guess we could link from dlang.org to some. -- Andrei
>
> A simpler solution is to to just link to this page, that contains the
> links to all pages that contain D entries:
>
> http://rosettacode.org/wiki/Category:D
>
> Bye,
> bearophile

Great, but I'm not seeing the PR. -- Andrei

On Thursday, 24 April 2014 at 16:23:22 UTC, Andrei Alexandrescu wrote:
> On 4/24/14, 2:20 AM, bearophile wrote:
>> Suliman:
>>
>>> It would be very nice to add to dlang wiki comparison woth Python, to
>>> show that D code can be easy as Python.
>>
>> In the Rosettacode site there are around one thousand Python-D comparisons.
>>
>> Bye,
>> bearophile
>
> Guess we could link from dlang.org to some. -- Andrei

It's much better to add best examples at wiki.dlang.org it's would be much easy for new comers to get info there than on 3 -parts sites. And program code is good, but would be very good to examples of simple algorithms like intersect to arrays, find copies in arrays, create thread and so on.

Very often I am googling such info because I know how to do it in one language and have now idea how to do it's in D.

Suliman:

> It's much better to add best examples at wiki.dlang.org

I am updating the examples on Rosettacode almost daily (example: I am currently modifying tens of entries to use @nogc). So you Suliman do you want to keep updating the dwiki to follow the very frequent changes in the rosettacode entries code?

Bye,
bearophile

On Thu, 24 Apr 2014 17:08:40 -0400, bearophile <bearophileHUGS@lycos.com> wrote:

> Suliman:
>
>> It's much better to add best examples at wiki.dlang.org
>
> I am updating the examples on Rosettacode almost daily (example: I am currently modifying tens of entries to use @nogc)

I don't think this is a very good idea. The code should likely build with the latest released compiler.

-Steve

Steven Schveighoffer:

> I don't think this is a very good idea. The code should likely build with the latest released compiler.

Yes, sorry, I know this could cause some troubles, but if you think hard about the situation, you will see that this is currently the best (or less bad) solution. It was recently discussed in D.learn, but I can't find the thread. So let's not discuss it again, because the conclusion will be the same.

Bye,
bearophile

Steven Schveighoffer:

> I don't think this is a very good idea. The code should likely build with the latest released compiler.

Oh, if you want to help rosettacode efforts, then try to fix this entry:
http://rosettacode.org/wiki/Parallel_calculations#D

Bye,
bearophile

On Thursday, 24 April 2014 at 06:38:42 UTC, Suliman wrote:
> Does anybody make tests of speed most common algorithm in D and Python. I am trying to understand which project better to start in Python and which in D.

I think I split my decision based on the tools available. So I'd probably write a website in Django instead of vibe.d because I would save a lot of time. I'd probably write D instead of Python in a lot of cases.

More than just for speed, I've come to appreciate type information and what I call "statically checked duck typing," which is how ranges work and so on. In D I can write code such that I can know very early on that it has a good chance of actually working. In Python, I often find out about problems too late, and I have to rely on tests with good code coverage to make sure that very basic code works at all.

On 24/04/14 23:49, bearophile wrote:

> Yes, sorry, I know this could cause some troubles, but if you think hard
> about the situation, you will see that this is currently the best (or
> less bad) solution. It was recently discussed in D.learn, but I can't
> find the thread. So let's not discuss it again, because the conclusion
> will be the same.

An ugly hack is to add a @nogc UDA.

-- 
/Jacob Carlborg

On Thursday, 24 April 2014 at 06:38:42 UTC, Suliman wrote:
> I am following discussions about GC and some other 'critical' improves in D language for a long time. I see a lot of arguments and heaps of code, that often hard to understand (for example Templates) even more complicated to use it.
>
> I like D, but more and more I am playing with Python, and understanding it's philosophy. And I like it because it's do not have any overhead like C++. It's clean any easy to understanding. As result it's harder to write bad code in it.
>
> Does anybody make tests of speed most common algorithm in D and Python. I am trying to understand which project better to start in Python and which in D.

In my experience, it is better to start a new project with D, not only because of speed. As a project grows, the restrictions of Python become more apparent (and annoying). If copyright is an issue, D is the better option, too. Python can be decompiled easily. I don't know what kind of projects you have in mind, but in our projects Python is always the bottleneck and has to be rewritten in a different language anyway, sooner or later.