On Friday, 22 July 2022 at 19:30:46 UTC, monkyyy wrote:

What's the dub here? My "cry from the heart" was about the impossibility of recommending D for anything in the slightest serious. Because of compiler development policy.

On Sunday, 24 July 2022 at 12:54:37 UTC, GL wrote:

Dub is D's package manager and build system

https://dub.pm/getting_started

On Sunday, 24 July 2022 at 12:54:37 UTC, GL wrote:

At this point, you're obviously trolling. You're complaining about a third-party package, not compiler development policy. But I do agree that - for some reason and with no supporting evidence - you repeatedly make the claim that nobody should use D.

Absolutely not!

The third-party package can not be assembled because of compiler changes.
Whereas two years ago ONLY the build was quite successful.

Many C++ library code from 2000 and even 1996 are still assembled without any changes.

Python library, formed in 1995 -- 2006, was useably up to new ages of Python 3 without any problem.

This made it possible to form a large code base.

And in our case, we have unpredictable and catastrophic obsolescence of the code within a couple of years or even less. Actually, any code can explode unpredictably at any moment. As a result of compiler changes. Isn't this the result of policy? Doesn't that make serious use in real life impossible when you have to use third-party libraries extensively?

I never said anything like that. I'm just stating the obvious --- such rapid and undetectable code obsolescence is absolutely disastrous for the reputation of the compiler and the whole D's ecosystem. This is purely a result of politics.

On Tuesday, 19 July 2022 at 09:18:12 UTC, GL wrote:

Anyone is going to fork it for maintenance purposes?
There are several packages that need to be updated.. and many others have libasync and memutils as a dependency

On Monday, 25 July 2022 at 05:56:00 UTC, GL wrote:

do you also complain that C++ is unusable because they constantly change up their language and standard library?