Re:More powerful Go execution traces
by the_gipsy on Friday March 15, 2024 @12:02PM
(#39717267)
Sounds a bit apologetic. I don't think that the ecosystem decided. The language creators decided, and the ecosystem couldn't do much about it.
[ Parent
| on HN ]
I say ecosystem to mean the majority of packages. That's the ecosystem.
Go's development process is fairly open and democratic though; if enough people flag it up, and if a case can be made for stack traces, it can be added.
As it stands though, the consensus is that it doesn't add enough value, it's too expensive (cost/benefit), errors are normal program flow, and 3rd party libraries can add the functionality if one decides they need/want it in their application.