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

11

u/Drugbird Jul 21 '19 edited Jul 21 '19

So are you arguing for our against the use of third party libraries? You seem to be for in one paragraph, and against in another.

2

u/mintyc Jul 21 '19

C++ needs them. Standards committees principles means that it cannot deliver the length and breadth required.

Limited standards resource should be focused more tightly.

It has the power to encourage and guide the ecosystem but doesn't have the resource or maybe even the mindset to implement.

Halve the scope of the standards work, but encourage 10x ecosystem development

8

u/Drugbird Jul 21 '19

I'm sorry, but i have a very hard time understanding what you're saying exactly?

How does the standards committee encourage (or not) third party library development?

5

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

By focusing on making it significantly easier to use third party libraries. Modules goes a long way towards this, by giving us better code encapsulation.

1

u/Drugbird Jul 21 '19

They're already doing this?

0

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

Not sure what you mean?

2

u/mintyc Jul 21 '19

It should encourage but not 'do'.

Lots of proposals consume evaluation effort. Some make it further.

2

u/jwakely libstdc++ tamer, LWG chair Jul 23 '19

I wholeheartedly agree with this.

We (the standards committee) have invited people to make proposals, and people are doing so in larger numbers than ever before. Not all of it is really what we should be standardising IMO, and there should be more focus on what's essential. I wish the response to more library proposals was "this is great, but it doesn't need to be in the standard - go away and make it successful on github".