Understanding Available Packages

[4141done]

Hi folks! Thank you for your hard work.

I am putting together some training that uses the instrumentation of NodeJS as part of its example. It's a very 101-level class. My two questions are:

1. I am seeking to explain to the audience the reason we have so many different packages for OpenTelemetry in NodeJS. Do you have any kind of statement on the design of the NodeJS telemetry libraries?
2. I'd like to help them understand whether they need a new package to accomplish their goal.

For (1) I have the following guess that I drafted that I would love to understand the accuracy of:

1. It's a big job maintaining instrumentation SDKs for so many languages and making sure that they are both high quality and up do date (remember the OpenTelemetry is an evolving specification). Therefore some of the separation of libraries could be to make keeping things up to date easier for the maintainers.
2. Instrumentation code always represents overhead and should be as lightweight as possible. By splitting things up into smaller pieces, the maintainers of the OpenTelemetry instrumentation SDKs are giving us the flexibility to install only the bare minimum of instrumentation code that is necessary for our use case.

For (2), is there any grand list of the packages and how they intersect? Currently I am just recommending that they go through the guides. The per-tool ones are self explanatory enough- but beyond the guides, and I can't find piece of documentation that might answer questions like "if I want to name my service, I need both the resources and semantic-conventions packages"

Thank you