package from. So if you create a new media player in Go and you include libopus,
you must put those .a files in your media player project directory.
+The advantage is that this puts the burden of managing libopus on the user of
+this go opus package (i.e. you), but not on the user of *their* program. In the
+media player example: you, the programmer, will have to manage the .a files, but
+the users of your media player can use those bundled .a files without having to
+apt-get or otherwise install anything related to opus. This is a worthwile
+trade-off as long as opus is not widely available for all major platforms, yet.
+
It can be changed
(<https://groups.google.com/d/msg/golang-nuts/lF5skXi7OD4/SjwQbgju91QJ>) but
that's on my TODO list for now, under "not worth the trouble until a lot of