D is our last hope

[jmh530]

On Tuesday, 19 December 2023 at 14:27:15 UTC, Adam D Ruppe wrote:
> On Tuesday, 19 December 2023 at 14:09:35 UTC, GrimMaple wrote:
>> So, I will reiterate: what would it take you to admit that D 
>> is more dead than alive and that something must be done about 
>> it?
>
> D could show it is still alive by merging these two PRs before 
> the new year:
>
> https://github.com/dlang/dmd/pull/15537
>
> Note that this one was approved at the August 2023 DLF meeting, 
> implemented shortly thereafter, yet still sitting in limbo.
>
> https://github.com/dlang/dmd/pull/15715
>
> This is the culmination of about 6 years of work by the D 
> community, yet is waiting on a pointless bit of red tape.
>
>
> So many contributors have been driven away by similar 
> situations. And it is going to happen again if they do not act 
> within the next twelve days.

I'm sympathetic to your frustrations on the string interpolation 
DIP (I don't know anything about the other one you mention). 
However, even if there has been a lot of work on and off for a 
number of years, that specific PR has only been outstanding since 
the second half of October. Most DIPs take longer than 3 months 
to get approved and language changes in other languages don't 
typically move that fast either (which isn't to say that D 
shouldn't try to move faster than other languages). Hopefully 
Walter can review before year end, but it seems like an arbitrary 
deadline to demand it be merged by then or you will no longer 
contribute. No doubt that DIP will be an uphill battle with 
Walter.

But I wouldn't disagree that with someone saying that D can 
certainly be a frustrating experience sometimes.

For some mir packages (no idea if this is a problem more 
generally), code.dlang.org won't catch updated tags without a 
force update. No idea why. But I only have the ability to force 
update some of them, but not all, and not the one I need to 
continue with what I've been working on.

I'm also confused why we can't come to some kind of agreement on 
issue 23479 [1]. That played out back in February and has been 
crickets since then.

[1] https://issues.dlang.org/show_bug.cgi?id=23479