October 19

On Saturday, 19 October 2024 at 03:21:43 UTC, Lance Bachmeier wrote:

>

On Wednesday, 16 October 2024 at 10:01:37 UTC, RazvanN wrote:

>

I'd wish we could fix all of these, but unfortunately, we just don't have the manpower.

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.

Well, some of us have itchy merge buttons and a willingness to bend a few rules to scratch that itch. Although my experience so far isn't that people mind the prettifying much, it's been more problematic when you suggest changes that are a bit more involved.

October 19

On Saturday, 19 October 2024 at 06:58:45 UTC, Adam Wilson wrote:

>

some of us have itchy merge buttons

https://issues.dlang.org/show_bug.cgi?id=20801
https://issues.dlang.org/show_bug.cgi?id=24307
https://gist.github.com/crazymonkyyy/432cf88729cd230fb0754b8d5b958653
https://gist.github.com/crazymonkyyy/6de535001d70a9bc45c0ea20913a38c1

October 20
On Tuesday, 15 October 2024 at 10:20:54 UTC, ryuukk_ wrote:
> and what's in you guessed right, more templates! yay!

Good old template paradox…
I’m starting to love it ;)


“The meta programming capabilites of D are unmatched and are essential…”
“I really, really like D's templating and metaprogramming.”

But at the same time:
“Wait… You’re actually using templates!? No, don’t. They are bad for you. Oh no, more templates!”
October 20
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
October 20
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.
October 20
On Sunday, 20 October 2024 at 00:14:25 UTC, Elias wrote:
> On Tuesday, 15 October 2024 at 10:20:54 UTC, ryuukk_ wrote:
>> and what's in you guessed right, more templates! yay!
>
> Good old template paradox…
> I’m starting to love it ;)
>
>
> “The meta programming capabilites of D are unmatched and are essential…”
> “I really, really like D's templating and metaprogramming.”
>
> But at the same time:
> “Wait… You’re actually using templates!? No, don’t. They are bad for you. Oh no, more templates!”

Just use more templates and also embrace compiler bugs, paradox solved
October 20
On Tuesday, 15 October 2024 at 09:07:12 UTC, Manu wrote:

> Ideally, we really need to be properly funding development for critical infrastructure... but I'm not sure we've ever had a sufficient budget to maintain that sort of commitment.

Which of the multiple donation destinations does the D foundation prefer these days for donations?  I see about four options and am not sure which is the preferred destination at this point.

Thanks,

October 21
On Sunday, 20 October 2024 at 21:20:14 UTC, Chris Piker wrote:
> On Tuesday, 15 October 2024 at 09:07:12 UTC, Manu wrote:

> Which of the multiple donation destinations does the D foundation prefer these days for donations?  I see about four options and am not sure which is the preferred destination at this point.
>

Whatever is best for you is the right answer. That's why we have different options. Some people can't or don't want to use PayPal, some people prefer OpenCollective in support of their mission, some people prefer GitHub because they are already supporting other projects there, etc.
October 21
On Monday, 21 October 2024 at 14:12:53 UTC, Mike Parker wrote:

> Whatever is best for you is the right answer.

Okay I've selected one.  Since I'm about to start using Visual Studio for a new project, Visual-D is something I'd like to support.  Thanks for putting visual-d upkeep on the front burner.
October 24
On Tue, 22 Oct 2024 at 03:26, Chris Piker via Digitalmars-d < digitalmars-d@puremagic.com> wrote:

> On Monday, 21 October 2024 at 14:12:53 UTC, Mike Parker wrote:
>
> > Whatever is best for you is the right answer.
>
> Okay I've selected one.  Since I'm about to start using Visual Studio for a new project, Visual-D is something I'd like to support.  Thanks for putting visual-d upkeep on the front burner.
>

The problem is that there is only one maintainer. He's not interested or
motivated by funding in the past.
In order for it to have a healthier existence, it needs more than one
maintainer, and if another could be motivated with funding then that's
something, but funding needs to be specifically directed to that person.
There's no dlang foundation effort to try and find/fund maintainers for
these essential projects.

The interesting catch that I reckon we can see with Visual Studio, is that
it's usually industry professionals that are using it, and as such they are
less likely to have bandwidth away from their work to work on that. It's
not an ecosystem that lends to hobbyists so much; the overlap in the venn
diagram between VS users and dlang hobbyists is small.
Ideally, a D company that uses VS should direct one of their staff to have
some hours dedicated to tooling... but there aren't any such companies as
I'm aware?