I think you're partially right.
I know this is not so black and white, but we could imagine there is
people which are familiar with open source and people which are not.
The first one will use the internal API but they will report the
issue to project developer too, the other will probably use the
internal API in silence. But if the internal API is not accessible
at all they will probably go in a lot of duplicated code to
workaround this, and you still not have your feedback :/.
There is also the case where the project is not so active as this
was the case for DLTK few years ago. In this case you could report
the issue to the community about the API issue, nobody will fix
that.
All of this was just thought, I let you choose what you prefer, I
just share my mind ;)
Le 01/10/2015 14:52, akurtakov a
écrit :
Hi Simon,
My only objection against x-internal is that people just use
them without getting involved with the project to help
getting proper API exposed and etc. And this is not good for
the liveliness of a project.
Regards,
Alex
|