>I used to think writing safe code in C/C++ was a matter of skill.

It's a matter of how many fucks the devs gave about doing quality work. You can find inexperienced people deliver quality work simply because they're passionate and they care (Half-Life was made in part by people with no prior game or coding experience), and you can find supposed rockstars deliver slop because for whatever reason they don't care, they just want to punch in, collect paychecks, then punch out.

FAANG stopped being a benchmark of skill a while ago. It's a skill of griding leetcode and 7 stage interviews to get it, then resting and vesting till you can jump ship to something better or get mass layd off.

▲

pfdietz 5 hours ago | parent | next [-]

> It's a matter of how many fucks the devs gave about doing quality work.

It's more a matter of how much management cares about quality, and how much time and how many resources they're willing to devote to it.

And that's a function of how much the quality of the code actually matters in the market.

▲

PorciiVorbesc 5 hours ago | parent [-]

FANG doesn't have resources, but indie coders and game studios do?

	▲	bawolff 42 minutes ago \| parent \| next [-]
		You can have all the resources in the world but it won't matter if you spend them on something else.
	▲	nxobject 4 hours ago \| parent \| prev \| next [-]
		I think you’re a bit optimistic about the quality of a triple-A game’s codebase that was rushed to a holiday release date. I have slightly more tolerance for bugginess in a game.
	▲	pfdietz 5 hours ago \| parent \| prev [-]
		Notice I said how much management is willing to devote, not how much they have.

▲

sczi 4 hours ago | parent | prev [-]

Has there ever existed a C or C++ codebase of significant size that hasn't had exploitable memory corruption issues? I don't think we can keep saying it's a question of the dev's passion or skill or whatever, if no dev has ever managed to do it.

That's not to say memory corruption issues are the only kind of issues, and rewriting a mature C/C++ codebase into a memory safe language may well introduce more issues than it fixes...