On 02.07.22 14:49, Eric Schirra wrote:
Old problems are not solved because they are too difficult or uninteresting. Instead, they take something new that is more hip, but doesn't have many functions yet or even bugs.
I'm totally with you on this. (This development model even has a name, coined by Jamie Zawinski almost 20 years ago: The CADT Model, https://www.jwz.org/doc/cadt.html). But gcc / glibc development can IMHO certainly not be put into that drawer. They actually go for the difficult things, as most easy things in the field of creating toolchains is solved for quite some time. And the feature of "complain about broken software we compile if FORTIFY_SOURCE=x is given" is working stably and correct if it rejects broken software. (I will totally retract everything I wrote today if the failure in nextcloud-desktop is in fact due to a false positive).
I am not against new things. I certainly don't. But it should take you further and not create new problems.
If the new feature is detecting broken software, and the software is actually broken, then unfortunately this will unveil an existing problem, even if it looks like it "has created a new problem". Best regards and have fun, -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman