Embracing the GC

I never actually liked the GC in D as it didn’t seem to fit in with the general direction of the language, and Walter Bright in D at 20: Hits and Misses says:

Miss: Emphasis on GC

Pretty much anything that’s only available via an app store. The difference with web apps is that I can also use them on a laptop/PC and I have a bit more control about tracking (by using ad/tracking blockers).

not being forced to have an Android or Apple smartphone, so more open standards and just Web apps instead of proprietary apps

I never really got used to IRC myself, but it’s usually fine when connecting to IRC via Matrix.

BTW, what other communication channels would you have expected?

Did a bit more digging through the mailing list (also looking through the links posted on the HN thread), and to me it looks a bit weird.

OP came up with an initial patch (Wed, Jun 1, 2022 at 12:36 PM) that wasn’t deemed to be good enough to be merged. Maintainer came up with a different patch (Tue, 7 Jun 2022 00:34:56 +1000) saying “but I wanted to fix it differently”. OP then posted a reworked patch (Fri Jun 10 17:15:49 AEST 2022) that looks a lot more similar to the maintainer’s patch.

The maintainer’s patch and OP’s reworked patch look quite similar, but from what I can see from the mailing list, the maintainer actually came up with that approach, and OP didn’t then credit the maintainer in his reworked patch. @kairos@programming.dev can you please clarify, what am I missing?

I am not really seeing any toxic behaviour here.

OP’s patch was largely based on code in ptrace32.c, but that code actually looks quite bad. So maintainer applied a better fix. Maybe ptrace32.c should be updated to use code that’s more similar to ptrace-fpu.c now?

So you have just re-posted an old email to the mailing list just so you can link to it, likely confusing everyone on that mailing list.

the email lists:

However, every one of these reports has to be triaged, analyzed, and dealt with.

I don’t think non-coding work means non-technical work - you’ll likely still need to dig deep into the technical details to actually be able to help

There is also a link to docs: add maintainer entry profile for XFS

and its linking ability is a huge simplifier for long term planning.

What long term planning? Who is going to come up with that plan? Will everyone agree to that plan? Who will be paying for the resources to work on that plan?

Combined with a Kanban board for tracking, progress of tickets. You remove a ton of pain.

I am not seeing how that would help. What are you going to do if there is no progress on something? Fire volunteer X because he didn’t make progress on ticket Y (as he has no interest in ticket Y)?

name[50] is out of bounds for char name[50]'

If it’s a YouTube video, it probably has been made to monetise, not to share tech material. So I usually avoid YouTube, because most of the time it’s not worth it.

I think it is Open Source now, see https://github.com/dlang/dmd

AFAIK the backend is based on the Zortech C/C++ backend and Walter Bright had to get permission from Symantec to relicence as Open Source.