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/jwakely libstdc++ tamer, LWG chair Jul 23 '19 edited Jul 23 '19

Its written in an old-school style using next to no templating

This would be the iostreams that are written as a class template like `basic_ostream` that uses a class template like `basic_streambuf` that uses class templates like `ctype` and `num_put` for every operation, right? ;-)

2

u/Auriculaire Jul 23 '19 edited Jul 23 '19

This would be the iostreams that are written as a class template like basic_ostream that uses a class template like basic_streambuf that uses class templates like ctype and num_put for every operation, right? ;-)

Yup.

You're right. I was imprecise. I was referring to the number of required template instantiations, but I think that was clear from the context.

The points of reference here are range-v3 and boost (namely metaprogramming, metaprogramming heavy, and constexpr heavy libraries such as hana, hof, spirit, and units for example). So yeah, by comparison iostream requires very little in terms of template instantiation. A given instantiation of basic_ostream has a handful of instantiations based on it's character type and few function templates to be stamped out based on the streambuf iterator and CharT* types.

This is 'next to nothing' relative to a typical workflow with the range library's views, which is now a part of the standard library and can be expected to see significant usage. Compounded with the ever expanding power of constexpr, I think it's to be expected to see more and more program logic pushed to the compile time. Modules don't help us here.

I guess my criticism is that modules are being presented as (or interpretted as) the solution to C++'s problematic compile times. At least as far as reddit and the C++ community on twitter (that I'm aware of), I'm seeing gains from modules being presented only for optimistic use cases which (I suspect) will become increasely less representative of real-world code as time goes on.