Roch Devost

> So I guess that higher values, 99 and 99.9.. percentiles are much more important for most users than lower values. Fair enough, but I would argue that I've never...

@felixfbecker Thanks for the review! > It seems like there is still manual code needed to propagate the spans, so there doesn't seem to be an improvement over the status...

> Could you link an example of a vendor API for scope management? I've only used Jaeger and LightStep which don't have one afaik I know at least New Relic,...

> So far I've used simple helper functions to manage spans The problem with this is that vendors can only implement existing methods, not add new ones. This is why...

Removed the implementation for `scope.bind()` to keep the base class as strictly no-op. This will allow vendors to implement it according to their needs, and eventually we can backport any...

@yurishkuro What should be done with this PR? Should we close it? There is a clear lack of interest to merge this feature and OpenTracing is scheduled to be deprecated...

I will definitely keep an eye open for the new project and port the scope manager if needed. @yurishkuro What is the best place right now to track the current...

I would argue it’s probably best to do at least 1 dynamic interpreted language at the same time as Java, as in my experience APIs designed solely for Java tend...

Here is a summary of the situation, along with the version support information asked above. ## Node modules The following Node modules exist and are popular enough to be mentioned...

> The most confusing and hard to implement thing is autoclosing scopes. And I'm not sure they really solve a meaningful problem. I don't think this is necessary at all...