[burntcaramel]

Instead of “harmful to performance”, why can’t we say “slow”?

Harmful should be reserved for things that affect security or privacy e.g. accidentally encourage bugs like goto does.

[jayd16]

"Considered harmful" is a meme they're referencing but yeah...its pretty stale at this point.

[Agingcoder]

To me it’s not a meme, it’s a reference to a very famous letter by dijkstra regarding goto statements.

https://en.wikipedia.org/wiki/Considered_harmful

[dwattttt]

Only once we convince C developers that a lack of performance isn't inherently harmful.

[DaSHacka]

More like Python / JS devs

C devs are the few I've met that seem to actually care.

[sim7c00]

maybe its not 'slow' but more 'generalized for a wide range of use-cases'? - because is it really slow for what it does, or simply slower compared to a specialized implementation? (this is calling a regular person car slow compared to an F1 car... sure the thing is fast but good luck takin ur kids on holiday or doing weekly shopping runs?)

[saagarjha]

glibc is faster in basically every usecase, though.

[masklinn]

“Generalised to a wide range of use cases” is a really strange way to say “unsuitable to most multi-threaded programs”.

In 2025 an allocator not cratering multi-threaded programs is the opposite of specialisation.