1. 8
  1. 5

    I find many of these articles disappointing and this article didn’t disappoint in disappointing.

    Most widely-used programming languages have at least one regular conference dedicated to discussing it. Heck, even Lisp has one.

    However, C is a notable exception. Despite its role as the foundation of the entire software ecosystem, there aren’t any regular conferences about C. I have a couple of theories about why.

    It’s false that C serves as any inherent foundation. Further, whenever you point out self-hosting compilers, people will worm their way through the source looking for any amount of C, however little, to claim that C really is the foundation, just as claimed. The fact that UNIX lacks any decent interface and forces C as one wherever feasible is entirely ignored. Even if you do eliminate C, the goal post is moved to the underlying operating system being written in C or even nodes in the network that it may travel through. Don’t you find it odd that just about the only positive thing you ever hear about C is that it’s popular?

    First, C is so fundamental and ubiquitous that a conference about C would be too general.

    You could claim that about many languages that do have conferences. Notice how this argument boils down to C being just too great for a conference. Any faults in C can never be the reason why something is so.

    Second, C has a tendency to be conservative, changing and growing very slowly.

    He mentions Lisp conferences earlier, entirely ignoring that Common Lisp hasn’t changed in over twenty years. This counterexample discounts this thought.

    In sum, rather than think about this critically, he gives many examples for why C is supposedly too good for its own good. I think my comment sums up the issues with this article nicely.

    1. 2

      Well there was once the Journal of C Language Translation while other languages do not get to have their own journal (even though I have some issues of the Perl journal). I guess it has to do with how things in a language get discussed and evolve. Some get journals and papers in academic conferences, some get dedicated conferences. You could discuss C stuff in a variety of places, like OS, Database and Compiler conferences so I guess this made the need of a dedicated conference redundant.

      Then other popular languages came along.

      1. 2

        Needs a culture tag perhaps.

        1. 2

          Probably not. Despite the question title, there’s little to no discussion of culture, but instead a list of good talks. The culture tag penalty hurts non culture content.

          1. 2

            There is no technical content in the article[*], nor in the comments to it in the usual places it was already posted. It addresses a community problem, even if the writeup itself is laid back about it.

            (*) Fair enough some of the linked material is technical, but it doesn’t reflect in the discussions that follow.

        2. 1

          I really like that before he posts his list he includes “I’m sharing them here so you can bookmark this page and never return again”

          1. 1

            “First, C is so fundamental and ubiquitous that a conference about C would be too general. “

            “Second, C has a tendency to be conservative, changing and growing very slowly. “

            These could be related a bit. I can easily imagine a conference for just C developers who exchange ideas on how to solve algorithmic problems, good tools, optimizations, analysis/verification, possible language improvements, and so on. Kind of like our C-related articles on Lobsters. ;) Then, author says:

            “The closest thing we have to a C conference every year is CppCon. “

            C++ is also getting updates. I don’t know if the conferences have any effect on facilitating those discussions or activities. If they did, then having conferences dedicated to using and improving C might have helped it.

            We also see a lot of growth in the Rust ecosystem coming right from their community and outreach work that had previously worked pushing Ruby. I think it’s darn-near a necessity if language developers want high innovation and growth. Not everyone wants that, C is fairly conservative as article states, and so maybe no here. Just saying it’s worth considering.