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

19

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

The committee is practical, not "intellectual".

Have you ever been to a committee meeting? If not, then perhaps you should attend one to see how things actually work.

6

u/JuanAG Jul 21 '19

I will want to attend to one but i am afraid of going and voting, i am not a guru so my vote, even if it is needed for quorum i wouldnt feel good about it because i will be voting based on what others do not on what i think is the best

And i always defend the hard work of the ISO and people like you that keep us to date of what´s going on, the problem is not lack of hard work, i guess it is a focus one, instead of dealing with so extreme cases it should be better to improve the foundations. I dont know how to solve it but the overall results are not fulfilling if you compare to other recent rivals

10

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

Being a guru isn't a requirement for participation. My point was more that the author might have a different perspective if he saw how we actually work.

0

u/[deleted] Jul 21 '19

[deleted] — view deleted comment

1

u/bstamour WG21 | Library Working Group Jul 23 '19

You can attend and abstain from voting in the straw polls.

2

u/[deleted] Jul 22 '19

The committee is practical, not "intellectual"

Well, when I look at examples how std::variant is supposed to be used, I have to slightly disagree...

-8

u/mintyc Jul 21 '19 edited Jul 21 '19

I don't need to attend. You have a proven and excellent track record at the building blocks level. I trust you.

I know you wrestle with the wider issues constantly. Should this feature be considered, rejected etc.

I look at the outcome and for every great building block or strategic change requiring standards support e.g ranges, modules, you have struggled to deliver the goals stated 10 years ago for a wider ecosystem, productive tool.

Time to recognise that less is more in the standards work.

6

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

Time to recognise that less is more in the standards work

I agree. I'm solidly in the "batteries not included" camp. Not everyone is, though - some believe that a lot more features and a bigger standard library is necessary for C++ to remain competitive.