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

[Adam Wilson]

On Sunday, 20 October 2024 at 00:32:05 UTC, Elias wrote:
> On Saturday, 19 October 2024 at 03:21:43 UTC, Lance Bachmeier 
> wrote:
>> Well, add some more bureacracy to the process, I'm sure that 
>> will fix it. We don't have enough people doing stuff but at 
>> least we have the prettiest codebases that follow all the 
>> rules.
>
> And more eventloop libraries. We need more eventloop libraries. 
> Not actual applications, just barebones stuff that wouldn’t 
> pass muster when eventually used in real-world apps. It only 
> needs to support this one unusual feature, the lack of which in 
> other libraries is someone’s pet peeve.
>
> (Oh, and image decoders. I feel like we don’t have enough 
> libraries to throw our JPGs and PNGs in yet. Especially on the 
> front of TGA we’re lacking.)
>
> There sure must be something wrong with the plenty of existing 
> libs, hence more and more are created. There surely is a 
> reason. Don’t let xkcd fool you. Really. “Comic #927? There's 
> no comic #927! There never was any comic #927! Comic #927 is 
> just a myth!”
>
> /s

I suspect that in many ways this phenomena is a result of of how 
much easier it is to build things like that in D. Don't like what 
anybody else built, why not build your own, it'll take less time 
than pretty much every other language out there (especially Rust) 
and you'll own it and can do whatever you want with it.

That said, it's also a sign, particularly on the data formats 
front that it's time for the standard library to step in start 
offering ... you know ... standards. Langauges with large 
standard libraries don't seem to suffer this fate as much, 
because in 99% of all cases, you would be better off used the 
standard implementation and getting about your actual work.