Re:Why I’m Using C
by worldsayshi on Friday March 13, 2020 @09:34AM
(#22567111)
I fear that we are slowly moving towards a situation where our underlying technology stack is written in languages that a diminishing number of people have seniority in.
96% of the Linux kernel is written in C (https://github.com/torvalds/linux).
Would be nice to get a survey of current Linux kernel maintainer demographics (age) and see where we're at. Can be good data for a call to arms and potential company backing via charitable funds.
The GitHub counters are not always accurate. 97.3% (if going by C (imp+header) and Assembly) of the kernel is written in C, with the rest being written in Assembly. Everything else is config files, scripts, tests, or docs. GitHub reports C++ and Objective-C; those are just .h header files.
Update: Got to my system so I could actually look at available files accurately:
C Implementation (.c): 28269
C Header (.h): 20250
Asm (.S): 1323
Edits: Update section and removing "100% in C" and "5 sources files of assembly"Eh, find -iname '*.s' in kernel source tree finds more than a thousand files and half a million lines in them.
I wasn't at my system when I wrote that and just checked (5 is way off the mark there). Should have followed my own advice and not used GitHub's counters :P
The counter reports 1.2%, but if you click on that to show Assembly files it only reported 5 code results (it's not actually showing all Assembly, so you then have to click on "Unix Assembly" on the side).
Pretty easy to integrate C libs as unsafe calls with rust's FFI. You're definitely in for an uphill battle if you have to manage a bunch of decade+ old makefiles with hundreds of special flags for each platform under the Cargo ecosystem, though.
In most cases, C would only be more practical on obscure or outdated hardware, though.