Subject: Re: [boost] Boost 2.0 ideas (was Re: Boost is supposed to serve *the entire C++ community; it isn't Boost's goal to serve Boost's c
From: Robert Ramey (ramey_at_[hidden])
Date: 2016-05-20 11:12:23
On 5/20/16 5:25 AM, Niall Douglas wrote:
Thanks for a good summary.
I <sniped> the whole thing in the interest of brevity. I don't intend
to address the specifics of the proposal here. It would be too long and
way too off topic. But I do have a couple of observations.
a) It's breathtaking in it's scope. You can't be accused of being
timid. Feel free to take that as a compliment.
b) There is no way Boost could get to this place starting from where we
are now by means of evolution. The gap is just too broad. You'll have
to think in terms of intelligent design rather than evolution. This has
been done before - after all boost itself was founded by a small group
of people who decided to strike out on a whole new path.
c) It would make just about every line of code in boost obsolete.
d) This would require resources on a scale way beyond what we've seen in
boost. Specifically, I'm thinking of library developers.
e) So I don't think that boost offers you anything for such a project
other than perhaps appropriating the name - which many of us would
object to. The story I got from the mouth of David Abrahams was that
original name "Boost" was morphed from "Booze" which was meant to
leverage on "Java". Pretty lame I know - but perhaps you could do
better for a name for your new project.
I doubt even forking boost would be of any help.
f) You're promoting a whole new vision - which I don't think will fly
with current developers, You'll have to convince a whole now cadre of
Given all this, I think you're efforts in this endeavor will be wasted
in boost and you'd likely get more reward starting something from
scratch. There is recent example of this as well. see Bartosz
Milewski's efforts to promote the next great thing.
Good luck with this.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk