Comment by Ygg2

20 hours ago

When triaging an issue you have to prioritise. Do you fix a problem that affects 2-3 people or one that may affect thousands?

The point is that such bugs shouldn't exist in the first place.

Using recursion on unbounded inputs on a programming language that doesn't support that (which are most) is an extremely classical mistake that really should be known to all programmers, especially those of low level languages that care about safety.

Every time you call something recursively you should be thinking "how deep is this?".

  • > The point is that such bugs shouldn't exist in the first place.

    That's true of every bug, but you don't have infinite time or manpower, so how do you prioritise?

By that logic, why even spend effort migrating from a known-working implementation to one which is known to have outstanding bugs that there isn't enough bandwidth to fix?

  • Hard to say, but there are legitimate reasons. One of which being they think Rust is growing while C is a shrinking language. Other could be safety (yes, yes the audit did surface bugs). Or even that having a single lib work seamlessly on Windows/Linux/MacOS/Redux/Web.