Gerhard Stöbich

I would never call `unpatch` in a production environment. There is no guarantee that it really does what one would expect. There were quite some discussions in the regard in...

Not sure if recommending NodeSDK is a good thing as of now. Besides the experimental state it comes with quite a lot dependencies like 4 trace exporters - but no...

What is the benefit in releasing new major versions frequently instead of new 0.x versions? People usually use something like `^13.0.0` so new majors are not picked up similar as...

ok so your assumption is that no breaking changes happen usually. The 0.x range supports this by incrementing patch and patterns like `^0.x` would work. As we are on 0.50.x...

> No, the semver spec makes 0.x versions special, in that breaking changes are allowed to be published in 0.x versions. So tools like npm etc. will not install v0.2.0...

if you use node in ESM mode it's needed to specify a loader, see [here](https://github.com/open-telemetry/opentelemetry-js/tree/main/experimental/packages/opentelemetry-instrumentation#instrumentation-for-es-modules-in-nodejs-experimental). This is still experimental and likely dependent on the node.js version so no guarantee that...

> Based on Typescript 5.1's [Release Notes](https://www.typescriptlang.org/docs/handbook/release-notes/typescript-5-1.html#breaking-changes), it seems that Node 14.17 is a minimum Runtime Requirement, as that version of Typescript emits Javascript that requires Node 14 or higher...

Another topic is likely the context manage. Hooks to get lifecycle of an request is enough to start/end a span and maybe even inject headers. But `ContextManger` requires to wrap...

I think for client http the req/res objects are bound on the context holding the parent span. This is because whatever is triggered in e.g. a `data` or `response` event...

If this ends up in SDK I would expect it to be similar across techs. If this happens it likely needs to be an optional component/api there because techs are...