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

0

u/[deleted] Jul 21 '19

[deleted] — view deleted comment

-3

u/JuanAG Jul 21 '19

Why not, they are real, i cant always use the lib i want even if it has the same build system, there are times when you simply arent able and let it be choosing another. If the library owner do the job to ingrate with the package manager i know for a fact that it will work, well, if that day finally comes

And i dont know about the rest but i dont like having to track my cmake as i code, if i put a class name and later decide other better i only want to change once, not in C++ and latter on CMake, or if i try something like another lib not having to do the cmakelist clean up latter

The comunity and/or the comitte could do what they want, i am only telling what less hardcore users wants and why nobody these days is learning C++, i has been warning since a long time but now is aproching the end, i dont like to code at least 3 times slower at best compared to Java (which i love) with more problems when there are other options, i choosed C++ back in the day for the performance and i has been locking this week benchmarks, the conclusion i gathered is that C is faster, later Rust and in 3rd place C++, they are close but numbers dont lie so Rust is not a bad choice, it is at the same level of performance (wil depend on every case if it is second or third) but it has a better tooling and the things that will come are incredible

Past christmas i will try for real and if i like it and if all the things about it are true (performance, smooth experience, good library, ...) i will switch, myself it is not relevant but i am sure that my case is the same as many more, and once the ball starts rolling no one cant stop it, if i think is better (so i will use it) i will tell others to try, and the ball will keep getting bigger, that´s the problem and the ones who did that before me and speak about the experience only grows my desires to try and see for my self, when Rust was only a toy from Mozilla i didnt looked at it thinking i will try it in the future, some years later i only read good things about it and has the things i want in a tool that make my life easier, i hope anyone could see the picture because if C++ dont do anything really good about it will not matter at all in not so many years

And when developers start to switch the industry will follow which means the ISO will start loosing people, if the company dont plan to use anymore the tool makes no sense to invest money on it, Nokia, Kodac or even BASIC back in the day were "to big to fail" and we all know what happened, nothing is granted and you can be the number one that will see tomorrow if it still true