Re:How to Structure C Projects: These Best Practices Worked ...
by jcranmer on Friday March 08, 2024 @11:31AM
(#39642712)
> The phenomenon of persistent derailment is, in fact, something that I had not seen until Rust arrived.
Apparently you have never seen a thread on X11, which almost invariably is derailed by a discussion about Wayland. Or in general, any discussion on Wayland or systemd is derailed into a rant how they're the worst software ever developed or something, to a tedious degree that makes me long for the Rewrite-it-in-Rust comments because at least those sometime make compelling points.
Re:How to Structure C Projects: These Best Practices Worked ...
by lelandbatey on Friday March 08, 2024 @12:52PM
(#39643680)
I also find that Go has delightful build tooling; running 'go build ./...' is nearly the universal build tool.
There, now we're not limited to just Rust advocates, so I hope you no longer find this thread sad : )
Re:How to Structure C Projects: These Best Practices Worked ...
by kerkeslager on Friday March 08, 2024 @03:58PM
(#39646400)
Agreed, go has good build tooling. And pretty good tooling in general.
And if you search my post history, you'll find some posts that make it clear I despise go.
As it turns out, languages aren't religions--you can like a language and admit it has flaws, and you can hate a language and admit it has strengths.
This makes no sense. Almost by definition, anyone derailing a discussion to mention $FOO is a member of the $FOO community.
It's disingenuous to suggest that all derailment is due to non-$FOO advocates.
> There is nothing new or sad about it.
The phenomenon of persistent derailment is, in fact, something that I had not seen until Rust arrived.
It is new, it's limited only to Rust advocates as a group, and I find it sad.