4 ms·

Large C codebases _have_ to be exceptionally nice, or they immediately collapse under their own weight. As a dev team, the language teaches you this the hard wa

Large C codebases _have_ to be exceptionally nice, or they immediately collapse under their own weight. As a dev team, the language teaches you this the hard way. I've never seen a terrible huge C codebase (but have seen many in other languages).

bigiain 4y ago
> I've never seen a terrible huge C codebase I have 100% confidence they exist. They just don't get uploaded to Github out of shame or embarrasment.
- fathyb 4y ago
  Proprietary device drivers come to mind..
  - SonOfLilit 4y ago
    They don't tend to be huge && in C
    - ventuspilot 4y ago
      AMD's linux graphics driver has entered the chat
- absolut-dolt 4y ago
- obudo 4y ago
  Can confirm they do. I worked at a company that was producing control systems for electric engines. Great environment and fun job but the code was beyond redemption. 15k line files with 2k+ lines #ifdef statements that ran different code for different customers, some variable names were just curses against pushy clients, not a single abstraction in sight. Not only they exist, they power massive machines that could crush a person in the blink of an eye.
- urthor 4y ago
  I think OP just found a really well done C file. You can definitely see many famous projects on GitHub, where even though the code is logical, you can't help feel it's a bit all over the place. cpython isn't all sun and roses. A broad generalization, but with C and C++ I'd say the standards for "good code" have dramatically risen in the last 10 years. Variable names seem to have doubled in size.
- e12e 4y ago
  > I've never seen a terrible huge C codebase libssl/openssl (before the rewrite/fixes especially)? Maybe doesn't qualify as huge? See eg: https://www.youtube.com/watch?v=GnBbhXBDmwU https://www.youtube.com/watch?v=GnBbhXBDmwU "LibreSSL with Bob Beck" (the first 30 days)

4 ms·

Large C codebases _have_ to be exceptionally nice, or they immediately collapse under their own weight. As a dev team, the language teaches you this the hard wa

by SonOfLilit 4y ago

bigiain 4y ago
> I've never seen a terrible huge C codebase I have 100% confidence they exist. They just don't get uploaded to Github out of shame or embarrasment.
- fathyb 4y ago
  Proprietary device drivers come to mind..
  - SonOfLilit 4y ago
    They don't tend to be huge && in C
    - ventuspilot 4y ago
      AMD's linux graphics driver has entered the chat
- absolut-dolt 4y ago
- obudo 4y ago
  Can confirm they do. I worked at a company that was producing control systems for electric engines. Great environment and fun job but the code was beyond redemption. 15k line files with 2k+ lines #ifdef statements that ran different code for different customers, some variable names were just curses against pushy clients, not a single abstraction in sight. Not only they exist, they power massive machines that could crush a person in the blink of an eye.
- urthor 4y ago
  I think OP just found a really well done C file. You can definitely see many famous projects on GitHub, where even though the code is logical, you can't help feel it's a bit all over the place. cpython isn't all sun and roses. A broad generalization, but with C and C++ I'd say the standards for "good code" have dramatically risen in the last 10 years. Variable names seem to have doubled in size.
- e12e 4y ago
  > I've never seen a terrible huge C codebase libssl/openssl (before the rewrite/fixes especially)? Maybe doesn't qualify as huge? See eg: https://www.youtube.com/watch?v=GnBbhXBDmwU https://www.youtube.com/watch?v=GnBbhXBDmwU "LibreSSL with Bob Beck" (the first 30 days)