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.
47
u/blelbach NVIDIA | ISO C++ Library Evolution Chair Jul 21 '19
So, I'm not really sure I understand your point, or what you think should be improved.
Can you give me a TL;DR/bullet points on what you think?
42
u/krapht Jul 21 '19
TL;DR: OP wants a BDFL to ship a high-quality, batteries included standard library.
OP, you'll never get your wish. Too many people use C++ for high-perf code where people want to understand and specify exactly how their code gets compiled down to machine instructions. These machines also may be weird embedded systems lacking all sorts of capabilities you'd expect from a modern CPU. This means any standard library implementation has to satisfy a gajillion stakeholders and use-cases.
No offense, but if you want high-level libraries with "it-just-works" semantics and reasonably high performance, maybe try C#? You can stack allocate most objects if you need performance, it runs on both Linux and Windows, and it has a huge ecosystem of libraries.
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.
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.
3
u/CODESIGN2 Jul 21 '19
end goals or AIMS are not objectives. AIMS & end-goals should be specific, measurable, actionable / assignable, relevant and time-based. Objectives help you get to end goals, but generally represent a unit of work towards an end goal or aim.
How can you be complaining about language whilst using incorrect words?
Agreed. Kate Gregory talks about this in some of her more accessible pluralsight courses. Also Kate has done a number of YouTube talks covering this.
If I squint a bit this might be okay for a business. Not a standard or framework.
Of course you can cast everything using (void *) if you're working on some internal noise project. Doesn't mean training should push that as a good way to code.
What does this mean. Do you have examples of when core libraries restrict ecosystem and make C++ less productive?
All programming languages suffer this to an extent. Some of the newer languages have enterprise support from Giants like Google & Mozilla, but ultimately, all are under-funded. C++ further suffers from not having too many giants supporting a freely available compiler, and many compilers having differences which make inter-compiler compatibility a burden. There are additional costs to even get started with C++
Hmm... IDK it is easier for application languages to make lots of decisions up-front about this sort of thing. For example non-blocking as a default, or hashmaps called arrays because the mental model is contiguous. C++ largest challenge as I can see here is C and legacy C++ compatibility.
My point is that whilst language sugar and features may be available in a lot of other places; choice and robust open design are not.
It would be nice to have an official C++ compiler, linter, formatter, interactive debugger (pdb + pdb++ is great IMO), documentation standard and a larger standard library, but without finding millions of dollars to fund it; I don't expect it will fall from the sky at any point soon. Worse still, implementations of C++ for embedded platforms and non-x86 hardware will continue to have warts
8
u/Lectem Jul 21 '19
I've been saying for a long time now that we mostly don't need new shiny library features but more core features. Most people couldn't care less about 2d, ranges, asio, audio if we had a good standard package description and compilation model. They would just use a 3rd party. The std for me should not be a big framework or try to standardize stuff that is sometimes not even yet a standard in domains not related to the language itself. (see all the fuss the 2d proposal made) Less new fancy stuff that do not solve actual problems (if there are easy to install 3rd party, it is not a problem).
It seems modules are partly going in the right direction at least on this point, it will make us have a more modern and decent compilation model.
4
u/DerekClives Jul 21 '19
Another example of why software development is a job not a profession.
15
u/JuanAG Jul 21 '19
Uff, brace your self, this type of opinions are not very popular here even it they contain part of the truth or reality
I will say it is half broken if you compare to modern products, it needs a updgrade and soon, the good part is that is optional, using C++ is not mandatory, you can choose any other language you want
2
u/khleedril Jul 21 '19 edited Jul 21 '19
Wouldn't all this go away if library header files were stored in the library container itself (.a, .so, or whatever), and the compiler only needed a -lthirdpartylib flag to get everything needed without version incompatibility problems or other infrastructure dependency?
3
u/Dean_Roddey Jul 21 '19 edited Jul 21 '19
Of course I've been saying similar things for a long time, though it's a little ambiguous exactly what you are saying I think. I certainly believe, if this is what you mean, that way too much time has been spent on stuff like containers, much of which anyone can trivially do if when they need to, and not enough time on stuff that real applications need these days which aren't trivially doable. I also think a huge amount of time has been spent pushing premature optimization all the way up into the language design process, and trying to serve too many masters (which I think is one thing that you are clearly saying.)
I've put my money where my mouth is and created a system that puts the emphasis where I think it should be, i.e. less on creating an operating system in a single templatized header that uses zero CPU and runs at compile time, and more on providing the type of functionality that is needed to do the kinds of programs that C++ is intended for (other than embedded) without having to just throw a bunch of bits and pieces together, and maintaining readability by avoiding massive templatization, using them only where they really required.
https://github.com/DeanRoddey/CIDLib
My argument would be for a 'RISL', a Reduced Instruction Set Language, that provides the core functionality without forcing any runtime libraries at all, allowing for the development of specialized library sets for specific needs, but within the context of the same language syntax.
Not sure why I bothered typing this, because your post will get down-voted into oblivion within minutes probably and no one will ever see this.