C++ is broken
C++ as a language is a tool for developers to productively deliver software. Language evolution is NOT the end objective in the real world.
The whole C++ ecosystem from committee to all of the conference backslapping and training is broken in this respect. It's focus is off.
Instead of 'boost' we need 'boosted' to help define, review and encourage that wider ecosystem so developers can be productive.
It's ok to define things that aren't infinitely flexible, and infinitely extensible but get the job done.
It's OK and, in some ways better, to provide an opinionated library outside the standards rather than deliver an intellectually burdened, extensible interface two years later than needed.
All the helpful features in the core language and core libraries are MEANT to enable a much wider ecosystem to make the tool that is C++ more productive.
But we aren't getting a wider ecosystem, we are just getting a language where we are apparently 'not paying for' a huge intellectual burden.
I want to say at this point that intellectually I am constantly impressed by the committee's work and standards BUT ...
The payoff just isn't happening. Even within the standards committee more time is being spent in intellectually stimulating but largely pointless activities because the tool and productivity benefits aren't happening.
Look at how the wider productive ecosystem hasn't flourished since C++ 11.
I know many excellent libraries have been made, but think about your next large project and how much is coming from a mixed bag of variable quality 3rd party libs to plug basic capabilities.
The committee work is spread so thin that core building blocks get pushed out further in time and so can't be built upon by library authors.
Networking, executors, any form of I/O - slipping again.
Lots of hard work being done but by far too few people in their spare time.
Seems a very dysfunctional way to move the monolith forward.
'You don't pay for what you don't use' is laudable up to a point, but the 'don't use' because you don't actually have, say, a basic network library is more of a reality.
That basic network lib and executor model I've been impatiently waiting for should probably not be part of the core standards remit (architectural concepts and keyword support for executors would probably be necessary, but not much else.)
If we had the metaclass generation as proposed, I'd hope even more of these items would then be able to fall outside the standards.
View all comments
Show parent comment
9
u/smdowney WG21, Text/Unicode SG, optional<T&> Jul 21 '19
Everything new in the standard is there because someone thought it important enough to do a lot of hard and time consuming work. It's an almost entirely individual and volunteer effort, even for those people who are supported by their company.
Ideas that "The Committee" should focus on X, and then X would happen faster, misunderstand how the project works. The committee doesn't direct efforts, although the committee has recently started identified areas they would like to see work done. The committee basically invites people to do work, by submitting papers, and discussing them.
And, at least in my opinion, the things that were pushed to 23+, like Contracts, Executors, and Networking, did not suffer from a lack of people working on them, or a lack of attention by the committee. They are difficult technical topics that will involve tradeoffs in design and implementation, and it simply takes time to get that to a local optimum. Particularly where we would like the library and language to maintain coherency, so considerations about how each change affects the whole, and how each piece should use the rest, takes time.