Feedback for this editorial cartoon

[IGotD-]

On Sunday, 26 January 2020 at 18:50:05 UTC, James Lu wrote:
> https://ibb.co/w6gQWwJ
>
> What other details could be added? I have some experience with 
> using Node.js as a systems language, so I can add that. I don't 
> have experience with Go or Rust, so I can add that.
>
> Thanks to the use of symbolic inclusion, I can very easily 
> modify this sketch

I don't agree with the picture in my opinion. I think that D and 
C++ have about the same complexity for beginners. You can program 
very C like in both C++ and D. However, when you start to tread 
into more complex territory, this is when the complexity of C++ 
exponentially increase. C++ projects tend to become spaghetti 
faster. D reduces this complexity compared to C++.

Big projects with a lot of files will probably benefit from D as 
D is more compact, readable and requires less files. The 
libraries of D are usually more convenient as well.

The reason I wouldn't use D in project is stability and 
availability of D programmers. All D compilers have bugs and are 
not as stable as GCC or Clang and I would not use D for mission 
critical projects and in this case C/C++ is a better choice for 
now.

It also depends on the projects. C/C++ is still king in low level 
programming and D has hard times to compete here. With 
applications it depends. D is held back by not having a true 
multi platform GUI library. C++ has Qt for example. When it comes 
other types of programs then D is really a viable option.

The picture is kind of simplistic and therefore cannot explain 
the complex decisions why a project should use C++ or D.