Ben Sigelman

@yurishkuro demonstrated support from three impls seems sufficient, though I wonder if it's "necessary" in many cases. So much of this depends on the complexity and impact of the proposed...

This is fun stuff, thank you for bringing it up. @hkshaw1990 I think the crux of this is finding a way to record only the performance data that's relevant when...

@hkshaw1990 sorry for the delay, I'm too busy these days :-/ For languages that support/encourage concurrency (Go, Java, C++, arguably Node.js), process-level measurements are better than nothing but not as...

@kriskowal this is important stuff, thanks for reaching out... I almost wonder if it would make more sense to have a quick call or something (happy to take notes and...

@adriancole a few thoughts: 1. I have always felt ambivalent about the "baggage" API. It's semantically profound (despite the seeming simplicity of the function signatures), yet also opens a Pandora's...

Thanks, @yurishkuro: I am confirming that the early time slots are 1pm _PT_, not 1pm _ET_, correct?

@kriskowal, one correction: > I believe it unwise because it establishes an ad-hoc global namespace shared by multiple services (as argued by @michaelsembwever and @bensigelman). This will cause request sizes...

Yeah. Not sure how others feel, but a capabilities struct – used responsibly! – seems like a net positive to me. (Side note: it would also help with, e.g., your...

(sorry for my delay getting to this) IMO we should not change core APIs for the *convenience* of wrappers. If there's a non-theoretical performance problem or something important is *impossible*,...

## Idea A How about a `HappensAfterSpan` and/or `HappensBeforeSpan` tag? The values would be span_ids or similar. To be sufficiently general, that would imply that span tags are `1:many` rather...