News for hackers. Stuff that matters.
Re:How to Structure C Projects: These Best Practices Worked ... by lelanthran on Friday March 08, 2024 @10:30AM (#39641940)
Every C discussion on the net always gets derailed by Rust proselytising.

No other language community does this to other language discussion. Even C++ fanatics didn't do this back when C++ was being sold as a C replacement.

This is an entirely new and somewhat sad, phenomenon: the need for the rust community to derail any and all discussion about some other language reeks of a community that feels threatened.

Re:How to Structure C Projects: These Best Practices Worked ... by twic on Friday March 08, 2024 @11:00AM (#39642282)
The comment you're responding to wasn't written by "the rust community", it was written by kerkeslager, who has written a bunch of C programs, but has found that the Rust build tools are better. There is nothing new or sad about it.
Re:How to Structure C Projects: These Best Practices Worked ... by lelanthran on Friday March 08, 2024 @11:08AM (#39642408)
> The comment you're responding to wasn't written by "the rust community"

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.

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.

Re:How to Structure C Projects: These Best Practices Worked ... by PH95VuimJjqBqy on Friday March 08, 2024 @01:39PM (#39644398)
It turns out, the rust community is made up of individuals. No one made the claim that there's some single entity called the rust community that's doing this. It's the individuals w/i that community doing it.

so yes, you pointed out the moniker of the individual doing this. It doesn't obviate the point.

Re:How to Structure C Projects: These Best Practices Worked ... by keybored on Friday March 08, 2024 @02:11PM (#39644923)
Every <lang> discussion here gets sidetracked/sidethreaded by <lang2> mentions.

- Rust? Why not Nim?

- Nim? Why not Zig?

Re:How to Structure C Projects: These Best Practices Worked ... by kerkeslager on Friday March 08, 2024 @02:55PM (#39645562)
1. I've written, at most, 10,000 lines of Rust. Calling me "the Rust community" is quite a stretch.

2. For comparison, I've almost certainly crossed the million lines of C mark years ago--if anything, I'm the C community.

3. You and I remember very different things about the C++ community. In fact, I also remember a number of other languages being offered as alternatives to C over the years including some obvious ones like Pascal or Basic, and also including some real absurdities like Lua (nothing wrong with Lua, but it's really not for the same kinds of projects as C). The idea that comparing your language to C is some sort of new phenomenon, is flat wrong.

4. You're ascribing a lot of intent to me bringing up Rust which isn't there. I'm not trying to derail the discussion--if you want to talk about C, do it.

5. The idea that the Rust community is threatened by C is a bit bizarre.