We don't want users (especially non-JVM/Python users) needing to know about or configure the internals, details like:
Java (and JVM memory management)
Vert.x (for example, Vert.x timeouts are mentioned in the docs as something the user can and may have to configure)
JVM logging
Maven
In addition to the usability issues caused by this, it has the downside that some internal changes become breaking API changes for the user.
We should review our codebase/configuration and identify exactly where the "internals" leak out into the public API, and see what we can do about each of them - usually adding a layer of abstraction on top of the internal configuration options.
agibsonccc
commented
4 years ago
We don't want users (especially non-JVM/Python users) needing to know about or configure the internals, details like:
In addition to the usability issues caused by this, it has the downside that some internal changes become breaking API changes for the user.
We should review our codebase/configuration and identify exactly where the "internals" leak out into the public API, and see what we can do about each of them - usually adding a layer of abstraction on top of the internal configuration options.