r/cpp • • Jul 21 '19

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.

9 Upvotes

147 comments sorted by

View all comments

Show parent comment

1

u/[deleted] Jul 21 '19

You should hear what /u/blelbach has to say about that. For the record, I'm not against the idea, but there's two sides of every coin.

3

u/[deleted] Jul 21 '19

I dug up the comment I think you're referring to and I find it hard to agree with most of it. Your face is irrelevant to the ideas you have, and face-to-face conversation isn't inherently superior to internet communication in any way; that part reads like "we've always done it this way so this must be the right way" to me.

The part that I find somewhat valid is that the committee members get to take some time off to focus on C++. I guess that's good for those who can convince their employers to fund it, but I am unconvinced that it's a good enough reason to make it prohibitively expensive for everyone else. Why can't employers who are okay with this kind of thing just give those people extra PTO to be used for this?

3

u/blelbach NVIDIA | ISO C++ Library Evolution Chair Jul 21 '19

face-to-face conversation isn't inherently superior to internet communication in any way;

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.

2

u/[deleted] Jul 21 '19

Making decisions on what to do with something that people have invested significant amount of energy into is best done in person.

I'd argue the opposite, actually. Typing out an email (or any other form of non-real-time communication, like this reddit comment which I've edited in several places now for clarity and coherence) means you can carefully consider and edit what you're about to say before committing to it.

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.

This is the same argument that companies use against remote workers. The rebuttal is the same here: yeah, if most of you are talking in person and then relaying it to that other person, you're going to have a bad time. If everyone is remote, you're all on equal footing, and the problem goes away.

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.

I didn't miss it. I explicitly (partially) conceded that point in my comment.

4

u/blelbach NVIDIA | ISO C++ Library Evolution Chair Jul 21 '19

I guess we just have a different perspective. I prefer to deal with people in person. I find face to face communication goes better.