The author never actually explains why not paying for what you don’t use will lead to the decline of C or C++. The author just says solving problems is hard in C and C++ and the ecosystem isn’t so great. That is a completely different point.
Not a very good article, IMO.
I guess the train of thought goes along these lines (always difficult to summarize the content in a title):
The motto don’t pay for what you don’t use is certainly true in terms of potential of the languages and the achievable resources efficiency, but totally misleading in terms of development process, its efficiency, and the useless time someone has to pay for. And C++ is the highest-paying programming language.
I guess I just don’t understand the premise of the article. These are the exact reasons someone uses C or C++.
You are right, the title of the article was pretty confusing. Now has been changed. It has also been extended a bit the reasoning behind it: it is more efficient in terms of CPU speed and memory, but not so efficient in terms of development time. And other languages, especially Rust IMO will get nearly as much efficiency in 90% of the cases, and development will be less painful. So those modern languages actually have the potential to produce the Sunset of C and C++, and the premise is that is not mainly because of the syntax of the language or cool features as safety, but due to the build and dev tools around it.
Because not only CPU cycles count, but also developers’ time
No kidding! This has been the standard industry perspective since the 2000s, at least. Why do you think Python and Ruby are so popular??
Thats the point of the article. Up to now, Python and Ruby had the cool features of modern dynamic languages plus nice dependencies managers that makes developing with them a pleasure (I love python too, I develop many hours a day with it since 2 years ago), but their performance was clearly inferior. But now, Go and especially Rust have both things, modern features, compiled and efficient binaries and builtin features for managing dependencies. And it seems that a large part of the communities of C and C++ have still not realized it, and they are excited about the evolution and modernization of the languages, but dont pay the same attention to the other components that actually account for most development time inefficiencies. And that could change the trends in computing languages and cause a decline in C and C++ usage. I think so, and was trying to convey this idea to C and C++ audiences. It is likely that I havent succeeded in the task, I am probably not good at expressing myself writing posts, I prefer writing code, not posts :)