5 ms·
> Anyways, not having correct stack traces is a HUGE no-no in production code I think that’s misleading. Not having a comprehensive stack trace is much more p
by macintux 7y ago
> Anyways, not having correct stack traces is a HUGE no-no in production code
I think that’s misleading.
Not having a comprehensive stack trace is much more painful for imperative or especially OO code, where the state at the time of failure is practically impossible to discern.
Erlang gets away with it (for decidedly non-trivial production code like much of the world’s cellular routing) because state is much easier to determine.
(Or maybe I’m blowing smoke. Certainly that’s how it feels to me.)