VisualD regressions are severe; what do we do about critical infrastructure?

[user1234]

On Friday, 18 October 2024 at 01:06:07 UTC, Adam Wilson wrote:
> On Tuesday, 15 October 2024 at 10:20:54 UTC, ryuukk_ wrote:
>> On Tuesday, 15 October 2024 at 09:50:06 UTC, Adam Wilson wrote:
>>> Got a spare 500k/USD/year? That's probably what it would take 
>>> to staff the essentials.
>>
>> Typical american mindset, "we only hire people from the Bay 
>> Area or Washington, and they cost us 500k USD a year, deal 
>> with it", "oh we out of funds, call the VCs we need to hire 
>> 100 more people"
>
> There about half-a-dozen people who work on D part-time, 
> uncompensated, on projects that are marked as critical to the 
> DPL/DLF. This does not include myself. 500k is a bare-bones 
> budget to support them.
>
> Or are you suggesting that we should all give up our day jobs 
> and work on D full-time and unpaid so that you can get your 
> free goodies faster? [...]

In my opinion the problem is not money, the problem would rather 
be the lack of people involved.

Example: the d-lang community org on GH (DCD, D-scanner, i.e most 
of the projects initially created by Hackerpilot, sure there's 
also D-YAML...) has the same problem as VD now. At the beginning, 
let's say during the first three years, that worked fine but at 
some point initial maintainers started being less focused but at 
the same time what was happening was a lack of contributors 
renewal. "No next-gen", to summarize.

By analogy: VD is maintained by one developer, this developer 
does something else, "bam", the project stalls.

Open-sources projects in the D ecosystem barly manage to create 
emulation. Beyond the compilers and the standard library it's 
most of the time single-man projects.