Why Aren't There C Conferences?

Post by pjmlp » Thu, Nov 22, 2018, 10:09 AM UTC

lscotte wrote: post #274

SiVal wrote: post #222

Earlier quoted context omitted.

To find the answer, I would ask, Why are there conferences for other technologies? What are they for? And I think the answer is probably 1) get useful news about recent and upcoming changes and 2) to socialize. I'm going to guess--possibly just projecting--that most C developers are older and not terribly interested in meeting new "C friends" or jumping into some hot, new "C startup". That leaves #1. Web/AI-ML/cloud/…

I think there's a third one: To generate hype. C is already established - it's been around long enough that it doesn't need advertising.

Post by pjmlp » Thu, Nov 22, 2018, 10:27 AM UTC

andy_ppp wrote: post #265

Because C is simple and not very interesting without an associated topic? I’m also not sure what you’d sell to C programmers. But maybe there should be one - with some good marketing it could do quite well I suspect.

Post by lloeki » Thu, Nov 22, 2018, 11:11 AM UTC

icedchai wrote: post #131

skykooler wrote: post #116

Earlier quoted context omitted.

Go is written in Go, which is why you need it installed in the first place before you can run the go compiler.

Except for versions before 1.5, which were written in C.

Post by mscasts » Thu, Nov 22, 2018, 11:42 AM UTC

Felz wrote: post #270

rickycook wrote: post #212

Earlier quoted context omitted.

and off a bridge? sounds like a JS conference

I can't resist. C conference: Address is past the end of the street. C++ conference: Reading the address requires working out an elaborate series of compile-time templates that finally resolves to the actual address. You go there to find that it's past the end of the street. JS conference: The address is "the last place we held it". You attempt to figure out what that means, but you didn't attend last year. After som…

Post by mscasts » Thu, Nov 22, 2018, 11:50 AM UTC

beat wrote: post #91

lostgame wrote: post #57

Earlier quoted context omitted.

What on earth are you talking about? Assembly. Java. Ruby. Python. The list goes on. Could you explain your rationale behind this statement?

Point me to a compiler or interpreter, any of them, that isn't either written in C or written in something that was written in C. And of course, whatever you play with, it's running on an operating system written in C. If programming is turtles all the way down, C is the bottom turtle, standing on the solid ground of Von Neumann architecture. The point is, C is utterly pervasive. Everything that we think is different…