In fairness, I think a lot of GIL languages already have high overload and I've never been under the impression OTEL was optimized for performance and efficiency.

It really isn’t. The code reads like it was designed by SpringBoot users. You have to read three different docs to suss out how to use multiple calls together to get a desired approach, and some of the docs leave out critical details. I think people forget that folks use Google thinks is the top result isn’t necessarily what the creators would assume is the document people would find for a topic. I’ve been trying to explain this to the Elixir community for instance.

“Can’t to X, doesn’t work.”

“Look, it’s easy. Did you even RTFM? http://blah.example.com/doc/articleb#section2”

“Uh, no, because search engine took me to http://blah.example.com/doc/articleg#section7”