4 ms·

Security teams 10 years ago: Hey, why are you using that library? Security teams today: Hey, why are you using that language?

cookiengineer 4y ago
Once the same kind of programming mistakes reappear in every other library, all over again, you start to question the language paradigms. Humans are not good at programming. I've never seen a "done" C++ codebase in my life, maintainers are always too busy reinventing parts that had originally nothing to do with the feature scope of their library.
- jlarocco 4y ago
  > Humans are not good at programming. I've never seen a "done" C++ codebase in my life, maintainers are always too busy reinventing parts that had originally nothing to do with the feature scope of their library. No reason to limit to "C++" there. It's an industry wide problem with every language. Even in open source, if a repo hasn't had commits in the last week, most people treat it as a dead project.
  - cxr 4y ago
    > if a repo hasn't had commits in the last week, most people treat it as a dead project By "most people", you mean GitHub-era folks who are secretly more interested in the things about the site that fulfill their social needs than they are interested in solving the problem that the software is supposed to be used for.
- treeman79 4y ago
  I can’t even imagine getting back into C and knowing where to begin to do it “right” and get to a useful level.
- jfhufl 4y ago
  I think that's the major problem with software engineering in general: when is software "done" ?
  - nmz 4y ago
    When you can no longer remove anything else.
pjmlp 4y ago
C.A.R Hoare in 1980, "Many years later we asked our customers whether they wished us to provide an option to switch off these checks in the interests of efficiency on production runs. Unanimously, they urged us not to--they already knew how frequently subscript errors occur on production runs where failure to detect them could be disastrous. I note with fear and horror that even in 1980, language designers and users have not learned this lesson. In any respectable branch of engineering, failure to observe such elementary precautions would have long been against the law."
TheLoafOfBread 4y ago
Security teams in 10 years: Hey, why are you programming?

cookiengineer 4y ago

Once the same kind of programming mistakes reappear in every other library, all over again, you start to question the language paradigms. Humans are not good at programming. I've never seen a "done" C++ codebase in my life, maintainers are always too busy reinventing parts that had originally nothing to do with the feature scope of their library.

jlarocco 4y ago
> Humans are not good at programming. I've never seen a "done" C++ codebase in my life, maintainers are always too busy reinventing parts that had originally nothing to do with the feature scope of their library. No reason to limit to "C++" there. It's an industry wide problem with every language. Even in open source, if a repo hasn't had commits in the last week, most people treat it as a dead project.
- cxr 4y ago
  > if a repo hasn't had commits in the last week, most people treat it as a dead project By "most people", you mean GitHub-era folks who are secretly more interested in the things about the site that fulfill their social needs than they are interested in solving the problem that the software is supposed to be used for.
treeman79 4y ago
I can’t even imagine getting back into C and knowing where to begin to do it “right” and get to a useful level.
jfhufl 4y ago
I think that's the major problem with software engineering in general: when is software "done" ?
- nmz 4y ago
  When you can no longer remove anything else.

pjmlp 4y ago

C.A.R Hoare in 1980, "Many years later we asked our customers whether they wished us to provide an option to switch off these checks in the interests of efficiency on production runs. Unanimously, they urged us not to--they already knew how frequently subscript errors occur on production runs where failure to detect them could be disastrous. I note with fear and horror that even in 1980, language designers and users have not learned this lesson. In any respectable branch of engineering, failure to observe such elementary precautions would have long been against the law."

TheLoafOfBread 4y ago

Security teams in 10 years: Hey, why are you programming?