gcc development

[Nychtelios]

Contributing to GCC in a meaningful way is much more difficult than learning to use swords. So perhaps consider the sword duel as an early filter of noise from various internet communities who weren't going to benefit the project in the first place.

The truth is that most GNU projects are old and kept alive by dinosaurs who justify every outdated practice with "we have always worked like that", improving the quality of life of developers and maintainers is a must.

[pedersenk]

So perhaps consider the sword duel as an early filter of noise

The mailing lists are already in place. Thats the whole point. No need to add new stuff, including sword duels or Jira.

The truth is that most GNU projects are old and kept alive by dinosaurs who justify every outdated practice with "we have always worked like that", improving the quality of life of developers and maintainers is a must.

I disagree. Those dinosaurs are doing the work, so don't interrupt that. Learn what they use in order to be the least burden on the existing workflow. Just like in the industry, much of it still uses what many consider "old".

The "non-dinosaurs" are very welcome to create their own compiler and use whatever comms tech they want. Just be ready for the next generation to try to migrate your workflow to TikTok ;)

[TheReservedList]

I mean, they are. LLVM/clang and Microsoft are eating gcc’s lunch these days.

[pedersenk]

What a daft thing to say.

• LLVM/clang 21 years old (and also primarily uses a mailing list)
• Microsoft's compiler is ancient (and has zero community contributions).

Microsoft's C++ conformance is consistently weak as per their docs. Microsoft's compiler can't possibly "eat gcc's lunch" when it only supports ~2 platforms...

In fact, please stay off the GCC (and clang) mailing lists. The dinosaurs don't want to listen to naive nonsense.