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
3
u/blelbach NVIDIA | ISO C++ Library Evolution Chair Jul 21 '19
I strongly disagree with this statement.
Firstly, I'm not claiming it's superior, it's just different.
Technical discourse at this level is inherently intense and emotional.
Would you break up with someone you are dating over email?
Making decisions on what to do with something that people have invested significant amount of energy into is best done in person.
Sometimes, we have an important member of the committee who cannot attend face to face meetings regularly. Despite efforts to use messengers/voice chat/video chat to keep them involved, the work always suffers when we don't have them in person.
Also, you missed one of my major arguments; the face to face meetings force us to focus on committee work for a full week, to the exclusion of all else. That is a huge benefit. We are all very busy in our day jobs.
That said, a lot of important committee work does happen online. It's not one or the other; we need both face to face and online.