Re: [boost] Future of C++ and Boost

[Robert]

It's time to refactor the IOS committee.

a) redefine it's mission.

Such a committee should address issues of the core language only.

b) "standard" libraries may be provided by anyone. Venders, Open Source fanatics, high school students, etc. They may be given away, sold or what every.

Since the language is already overladen with too many arcane features, the job for the IOS committee can be considered mostly done. The committee can shrink down to a manageable size. Getting your pet idea into the "standard library" to have other people code won't give you the excitement it once did. Oh well.

With the exception of “paid” standard libraries, how is this not already the case? WL

On May 11, 2022, at 6:28 PM, Robert Ramey via Boost wrote:

It's time to refactor the IOS committee.

a) redefine it's mission.

Such a committee should address issues of the core language only.

b) "standard" libraries may be provided by anyone. Venders, Open Source fanatics, high school students, etc. They may be given away, sold or what every.

Since the language is already overladen with too many arcane features, the job for the IOS committee can be considered mostly done. The committee can shrink down to a manageable size. Getting your pet idea into the "standard library" to have other people code won't give you the excitement it once did. Oh well.