My bad, I always mis-remember RhinoCommon as a C++ package. I wanted to refer to the issue that C++ sdk is not supported on macOS. See more discussion here:
What isn’t good?
Quite some through out the years:
(The logged 3-year-old issue is still open)
If you want more, I can provide more.
But as an end-user, I feels I spent much more time in digging into the use of the API and ask here in the forum for using the SDK, rather than just read a clearly written and maintained documents for all the usages and examples.
It definitely help me in solving some issues throughout the time, but I finally decided to get rid of it in my pipeline, because time is expensive.
And from my own experience, it seems McNeel is also not actively maintain and updating the SDK based on user feedback (for instance, check the logged issue you did 3 years ago).
You seems also have no interest in joining into the modern C++ package management system (vcpkg, git submodule etc.), and need the user to manually install additional packages. Neither is it easy to automate the task with GitHub Actions.
I understand as a CAD software company, you have valid reason to make these decisions. And I’m not among the majority here and perhaps am one of the few that really doing something that needs the performance of C++ . But clearly the developers are not treated as a very important role in your ecosystem.
If you want to collect more feedback and improve the product, I’m happy to help.