I think it is a little bit melodramatic as an analogy. It's perfectly fine to tinker with C, to use it in personal projects, to use it where it's not possible to use something safer (some embedded system that Rust doesn't have a backend for) or if you want to contribute to an existing project like Linux, OpenBSD or CPython. Whereas it's really not a good idea to work with Asbestos under any circumstances.

But the message overall - that maybe we don’t need to instinctively reach for C for newbuild low-level programming anymore - is probably about right

As long as it doesn’t have a modem you’re probably safe. Probably.

> Ouch, that's a hurtful analogy.

It's also wrong. A lot of the time the people making these types of comments about C are just plain bitter that their favourite $NEW_LANGUAGE is mostly a rounding error in terms of usage.

> A lot of the time the people making these types of comments about McDonald’s are just plain bitter that their favourite $3_STAR_MICHELIN_RESTAURANT is mostly a rounding error in terms of visitors.

> A lot of the time the people making these types of comments about McDonald’s are just plain bitter that their favourite $3_STAR_MICHELIN_RESTAURANT is mostly a rounding error in terms of visitors.

That's true too; what's your point?

The supposed bitterness doesn't actually make their criticism of McDonald's wrong.

I guess you need to know it enough to know why people don't want them now.

Like, everyone knows typescript catches more human mistake that JavaScript. But you won't know why if you don't know JavaScript at first place.

Were you planning to write production software on your 486? I don't see why it should hurt you at all.

If there's a joke here I missed it, sorry.