Jack Berg

I don't think anyone is going to argue that there aren't language-specific idiosyncrasies to work through. The "guidance" that this issue mentions might be better described as: a strong recommendation,...

Yes. For the purposes of obtaining a signal that a new proposed feature is correct and ready for stabilization, prototypes need to have a higher bar than an unmerged PR....

> Why can't users call the thing from the branch/fork that sourced the PR? Its definitely a grey area because with enough effort, anything is possible. The bar for a...

Very cool idea! Love the dropdown to toggle between different language options. Really hammers home the point that opentelemetry is a language agnostic toolkit. ![Screenshot 2024-10-10 at 10 06 14 ...

Hey I've been mucking around with a bunch of tooling lately causing all sorts of nasty merge conflicts, so I tried to make up for it by merging main and...

I'm not comfortable making these SPIs stable for a couple reasons: 1. The API for HttpSender, GrpcSender continue to churn. I'm not confident that we've reached the correct API contract...

> Are there any concrete plans to change this API in any way or is this just an hypothesis? Check out the history in the sender / providers: - [https://github.com/open-telemetry/opentelemetry-java/commits/main/exporters/common/src/main/java/io/opentelemetry/exporter/internal/grpc/GrpcSenderProvider.java](GrpcSenderProvider)...

> The JDK client manages its own Thread Pool and that inevitably leads to some overhead JdkHttpSender only sends synchronous requests (i.e. it never calls `sendAsync(..)`). I assume this means...

I am planning on working on this soon-ish.

@dashpole your comments made me realize that we have a more general problem to solve here. I've opened up #4142 to address, which supersedes this.