Marc Pichler

It looks like #3827 is not being worked on for now, so anyone who wants to pick this up would have to lay the groundwork for adding such an experimental...

AFAIK no one is currently working on this. Interest in it might pick up once the specification is marked stable.

> @legendecas Would it be acceptable to add Deno as a dev dependency for OpenTelemetry-js? If it is, I think Deno support could very well be added to the repository...

> You’re right adding Deno integration tests might be a less intrusive first step. From my personal testing, I found most things work with Deno already, but the reliance on...

@arendjr Thank you for the detailed answer. :slightly_smiling_face: We've talked about adding Deno support in the meeting yesterday, and I'll try to summarize what we talked about: **Not so good...

> Thanks! I've created the requested issue here: #4106 Thanks :slightly_smiling_face: Added it to the milestone to discuss, and we'll put the reasoning on the issue. > Totallly understandable about...

Not stale as we'd need to implement `OTEL_EXPORTER_OTLP_METRICS_DEFAULT_HISTOGRAM_AGGREGATION` after #3506 lands. :slightly_smiling_face: (we also need to address [the comment I made earlier](https://github.com/open-telemetry/opentelemetry-js/issues/3193#issuecomment-1274370136))

When this is done, we'll also need to update the [spec compliance matrix](https://github.com/open-telemetry/opentelemetry-specification/blob/main/spec-compliance-matrix.md) with the newly supported env vars.

The spec has now been clarified that the remote sampler is supposed to be included with an SDK implementation. I opened a new issue that should be a bit clearer...

This was fixed by #4157 and then the handlers were removed completely in #4438. Please let me know if there's any issues still and I'll re-open