Why Aren't There C Conferences?
nullprogram.com
Why Aren't There C Conferences?
1–10 of 383 posts
Re: Why Aren't There C Conferences?
#2All programming conferences are C conferences, if you think about it.
Re: Why Aren't There C Conferences?
#3Good question, but a majority of this post is links to cppcon videos. (I do appreciate the shoutout to LLVM).
I think the C community:
* Should have a C conference.
* Actually be more aggressive in adding features to the language. For example, there are some really great GNU C extensions that are long overdue be added to the standard. Compiler vendors should work with the standards bodies more, rather than shipping language extensions, compiler builtins, and various compiler plugins in isolation outside of standards bodies (because then codebases become tightly coupled to the compiler; ie. the Linux kernel).
Re: Why Aren't There C Conferences?
#4Because it is too broad for a targeted conference.
Re: Why Aren't There C Conferences?
#5Related tweet from last week: https://twitter.com/krzyzanowskim/status/1062740353533513728
Observation: Before 2014, iOS conferences were iOS conferences and was mostly about how to use the frameworks. After 2014, iOS conferences renamed to Swift conferences and everyone tries to figure out how to use Swift - like this is the main pain point or what?
Re: Why Aren't There C Conferences?
#6Good question, but a majority of this post is links to cppcon videos. (I do appreciate the shoutout to LLVM). I think the C community: * Should have a C conference. * Actually be more aggressive in adding features to the language. For example, there are some really great GNU C extensions that are long overdue be added to the standard. Compiler vendors should work with the standards bodies more, rather than shipping l…
The main problem with that is there is no single C community.
Imagine trying to get ANSI C, Win32 C, GNU C and every flavor of embedded C together.
Re: Why Aren't There C Conferences?
#7Because ioccc is either too cheap to rent a ballroom, or they're not too cheap but in following their theme and long practice, they aren't telling you when and where they rented one.
EDIT: It's true. HN has no sense of humor.
Re: Why Aren't There C Conferences?
#8Good question, but a majority of this post is links to cppcon videos. (I do appreciate the shoutout to LLVM). I think the C community: * Should have a C conference. * Actually be more aggressive in adding features to the language. For example, there are some really great GNU C extensions that are long overdue be added to the standard. Compiler vendors should work with the standards bodies more, rather than shipping l…
The main problem with that is there is no single C community. Imagine trying to get ANSI C, Win32 C, GNU C and every flavor of embedded C together.
Nonsense, that is the C community. They need to be put in a room together to sort out their differences. The differences exist due to communication breakdown which leads to divergence over time.
Re: Why Aren't There C Conferences?
#9Good question, but a majority of this post is links to cppcon videos. (I do appreciate the shoutout to LLVM). I think the C community: * Should have a C conference. * Actually be more aggressive in adding features to the language. For example, there are some really great GNU C extensions that are long overdue be added to the standard. Compiler vendors should work with the standards bodies more, rather than shipping l…
The main problem with that is there is no single C community. Imagine trying to get ANSI C, Win32 C, GNU C and every flavor of embedded C together.
Even the functional language communities arrange joined conferences to learn and exchange ideas, so why can't C?
Re: Why Aren't There C Conferences?
#10Related tweet from last week: https://twitter.com/krzyzanowskim/status/1062740353533513728 Observation: Before 2014, iOS conferences were iOS conferences and was mostly about how to use the frameworks. After 2014, iOS conferences renamed to Swift conferences and everyone tries to figure out how to use Swift - like this is the main pain point or what?
In my experience, they're still about frameworks mostly, they just brand themselves as Swift conferences to indicate there isn't going to be any Objective-C oriented content presented, so people don't attend with the wrong expectation.
Swift-oriented content at a conference is also going to be popular, as unlike frameworks, it affects every developer, as compared to frameworks where only a percentage may use each one.