This came in privately from Michael Richardson and is forwarded with permission:
> If you don't grow the user base, you decline. > As long as the old APIs do not go away too quickly, or the new APIs are > obvious refactors, then it won't be such a problem. > > In general, I think that there are way too many APIs, and the documentation > is poorly organized by what it does rather than what things it does it to > (more OOP). > I tried to collect notes at one point, I had other priorities. > > And I still have a pull request which is waiting for me to validate that it > works on VAX/VMS. Pauli -- Dr Paul Dale | Distinguished Architect | Cryptographic Foundations Phone +61 7 3031 7217 Oracle Australia > On 30 Oct 2020, at 9:43 am, Dr Paul Dale <paul.d...@oracle.com> wrote: > > At the OTC call on Tuesday Tim raise a point about the future direction of > the project. I was tasked with bringing this to the OMC for consideration. > > The question was should we design our APIs to ease the pain existing users of > OpenSSL or should we be trying to attract new users. > The idea being that supporting existing users means not changing the existing > API, whereas catering to new users means working towards a new fresh > consistent API. > > This is all in the context of function naming, argument ordering, cleanup for > beta 1. > > > Pauli > -- > Dr Paul Dale | Distinguished Architect | Cryptographic Foundations > Phone +61 7 3031 7217 > Oracle Australia > > > >