|
|
|
|
|
|
by ngrilly
818 days ago
|
|
|
Fair enough. The context is that years ago, my team was evaluating Go and Node.js as options for a server requiring concurrency, and back then Node.js didn't provide any stacktrace for async callbacks. I know it has been improved since then, but I don't use Node.js. What do you miss in Go's stack traces? |
|
|