disclaimer: otel maintainer, etc.<p>one thing I want to point out is that, eventually, we'd like for a lot of the complaints people have to be... well, things that you don't have to complain about, because it's not important. three or four years from now, it'd be nice to see a world where most people don't actually have to interact with otel at all because it's either built-in to the libraries/frameworks they're using, or because they're using some kind of wrapper that helps with best practices.<p>you can see an example of this with something we're doing at lightstep - we're introducing launchers that wrap upstream otel and standardize config format/defaults between multiple languages (<a href="https://github.com/lightstep/?q=launcher" rel="nofollow">https://github.com/lightstep/?q=launcher</a>), and trying to provide "missing link" documentation (<a href="https://otel.lightstep.com" rel="nofollow">https://otel.lightstep.com</a>).<p>i suspect that eventually the question of "how do i use opentelemetry" becomes a moot point because it's already there.