Re: Boost.Charconv review runs January 15th - 25th, 2024

From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2024-01-25 13:50:38

On 1/25/24 16:45, Vinnie Falco wrote:
> On Thu, Jan 25, 2024 at 5:41 AM Andrey Semashev via Boost
> <boost_at_[hidden] <mailto:boost_at_[hidden]>> wrote:
> 
>     Not that I oppose the sentiment of making life easier to users, but
>     OpenSSL is a project of its own, with a community of developers around
>     it. Making their library easier to consume should be their goal, not
>     everyone else's. If you have complaints or suggestions on this front,
>     you should probably take them to the OpenSSL developers.
> 
> I am not complaining about OpenSSL in particular, and the "we" to which
> I refer is the community of C++ library authors writ large. However in
> this case there is a specific pain point with respect to OpenSSL and b2
> which for better or worse is our responsibility and not OpenSSL's.
> 
> We could debate who is responsible for complaints or suggestions but at
> the end of the day users don't care; they need something that works. If
> an upstream provider can't get it together, pointing the finger and
> saying "it's their fault" is unhelpful.

It's not about pointing fingers, it's about fixing the problem where the
problem really is. If this problem is with b2 then let the b2 team work
on it (assuming they recognize the problem). If the problem is with
OpenSSL in general then no amount of work on b2 or Boost will fix it.