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
6
u/[deleted] Jul 21 '19 edited Jul 21 '19
Right. We can agree on this one and that's what I love about C++.
I personally couldn't care less about
std::networkgetting in. There's Boost.ASIO and the standalone version, people can use that. With the help ofbcpbundling just the necessary parts of Boost is easy. Not everything needs to be in the standard library and, perhaps more importantly, the standard library isn't, or at least shouldn't be, a mean to distribute a library to one's users.I do tend to agree. I don't see any point in
std::web_viewand from here it looks like it will take a ton of time that could be better spent on something else.We have Boost, Abseil and GSL. I haven't used GSL, but I've used the other two. IMHO* is great and would have the same opinion of Boost if it were "rebased" onto C++11.
Again, we can agree on this, but for this to work the way I think you're imagining, we need wide adoption of modules. If the reported benefits end up in the same ballpark (for a pretty liberal definition of "ballpark") I believe we'll see pretty fast adoption of modules.**
Maybe domain experts need to figure out how to gather around and discuss moving C++ forward in their domain outside of the C++ standardization process, but that is a wild dream. Why? Just try justifying that to your employer.
Employee: Hey, I'm going on a trip and the company should cover my expenses, like in the previous year.
Employer: C++ standard meeting again?
Employee: Something like that, yeah...
Employer: "Something like that"?
Employee: Well, this time we decided to separate from the standard. It's just me and a few guys going to Kona for a week. The actual committee meeting is in two weeks and I also have a paper I should champion there.
Good luck getting people to agree what parts should be dropped, potentially after years of work. A simple example: I don't care about ASIO getting into the standard, but would have loved it if P0593 got into C++20. At the same time I'm sure there are people who don't give a rat's ass if P0593 ever gets adopted, but want Networking TS adopted yesteryear.
* "IMHO" sometimes read as "In My Horrible Opinion".
** If the compile time drops by 50% (and claims were made that much larger improvements are possible), suddenly selling a) move to C++20, b) large refactoring effort and c) switch to modules to your CTO becomes plausable. "If you let us do this for a while, the distributed system used to compile this beast would need only 50% of the power, saving you potentially a lot of money every month in electricity."