Mastodon Feed
dysfun@treehouse.systems ("gaytabase") wrote:
okay okay, i'll go one further. when i do certain things in rust, memory safety pisses me off and i end up writing c in rust because i don't have the tools to express the api i need safely. or not at full performance at any rate.
hence why i have been doing a lot of c and zig recently. because there i can replace all that memory safety with "just learn to write c properly", which i conveniently already did.
because it works in the small, on a project of limited size, with a team of one person who knows c properly.
i think you can see probably see that this is not all projects and that the bigger everything gets the more room there is to fuck up. and so people accept the compromises of the safe-by-default languages because it's cheaper than the fuckups that tend towards guaranteed after a certain codebase size.