On Thursday, 13 January 2022 at 01:19:07 UTC, H. S. Teoh wrote:
> In the above example I literally just added ".parallel" to the code and it Just Worked(tm).

So did I for my weekend raytracer (I am new to D and was pleasantly surprised how easy it was).

    foreach (i, ref pixel; parallel(image.pixels)) {...}

On Mon, Jan 17, 2022 at 09:12:52PM +0000, bioinfornatics via Digitalmars-d wrote: [...]
> And recently I put my feedback where D could provide some killer feature in this area: https://forum.dlang.org/thread/fuzvsdlqtklhmxsnzgye@forum.dlang.org
> 
> Unfortunately, this will not be possible in the near future, so others language will keep the market

Why would it not be possible in the near future?

None of the items you listed seem to be specific to the language itself, it seems to be more of an ecosystem issue.


T

-- 
It is widely believed that reinventing the wheel is a waste of time; but I disagree: without wheel reinventers, we would be still be stuck with wooden horse-cart wheels.

On Monday, 17 January 2022 at 21:31:25 UTC, H. S. Teoh wrote:
> On Mon, Jan 17, 2022 at 09:12:52PM +0000, bioinfornatics via Digitalmars-d wrote: [...]
>> And recently I put my feedback where D could provide some killer feature in this area: https://forum.dlang.org/thread/fuzvsdlqtklhmxsnzgye@forum.dlang.org
>> 
>> Unfortunately, this will not be possible in the near future, so others language will keep the market
>
> Why would it not be possible in the near future?
>
> None of the items you listed seem to be specific to the language itself, it seems to be more of an ecosystem issue.
>
>
> T

Take one item on the list: developing an equivalent of numpy and scipy. What do you take to be the "near future"? One year away? Two years?

There is no language feature holding these items back. Addressing ecosystem issues is a massive undertaking.

In order for a D clone of even just numpy to be successful, it needs to have a significant user base feeding input back into the development cycle so that it can go beyond simply being churned out by a few overeager developers and actually stabilized so that it becomes useful and robust.

You must also consider that the items that bioinfornatics listed are all somewhat contingent on each other. In isolation they aren't nearly as useful. You might have a numpy/scipy clone, but if you don't also have a matplotlib clone (or some other means of doing data visualization from D) their utility is a bit limited.

His wishlist is a tall order.

On Tuesday, 18 January 2022 at 17:03:33 UTC, sfp wrote:
> [snip]
>
> You must also consider that the items that bioinfornatics listed are all somewhat contingent on each other. In isolation they aren't nearly as useful. You might have a numpy/scipy clone, but if you don't also have a matplotlib clone (or some other means of doing data visualization from D) their utility is a bit limited.
>
> His wishlist is a tall order.

Have you tried ggplotd [1]?

[1] https://code.dlang.org/packages/ggplotd

On Tuesday, 18 January 2022 at 17:24:03 UTC, jmh530 wrote:
> On Tuesday, 18 January 2022 at 17:03:33 UTC, sfp wrote:
>> [snip]
>>
>> You must also consider that the items that bioinfornatics listed are all somewhat contingent on each other. In isolation they aren't nearly as useful. You might have a numpy/scipy clone, but if you don't also have a matplotlib clone (or some other means of doing data visualization from D) their utility is a bit limited.
>>
>> His wishlist is a tall order.
>
> Have you tried ggplotd [1]?
>
> [1] https://code.dlang.org/packages/ggplotd

I haven't tried it. I also hadn't heard of it before.

Judging from the small number of GitHub issues it appears that it is used by basically no one and that it's missing crucial standard features supported by all mature plotting libraries. In one of the issues the main developer indicated he is no longer adding new features. This library seems to be: 1) quite young, 2) not actively developed, 3) not actively maintained.

On Tuesday, 18 January 2022 at 18:32:41 UTC, sfp wrote:
> [snip]
>
> I haven't tried it. I also hadn't heard of it before.
>
> Judging from the small number of GitHub issues it appears that it is used by basically no one and that it's missing crucial standard features supported by all mature plotting libraries. In one of the issues the main developer indicated he is no longer adding new features. This library seems to be: 1) quite young, 2) not actively developed, 3) not actively maintained.

Hadn't realized that. Shame.