He’s correct because as far as I can tell, blueprints are not a language.
No grammar and syntax. It is flowchart construction tool where flowchart is converted to executable code.
However, all the talk about “real” programming languages is nonsense.
It is newbie syndrome. “I learned a language and I want to feel special because of it” kind of thing. Most of the time it will be cured after years of programming, although in some rare cases it is incurable.
Actually those languages were created in order to use less-skilled people in software development. Not much point in trying to deny that.
It is like Rifle vs Longbow. Longbowman requires lifetime of training, while anybody can grab a boomstick, point it in general direction of target and fire.
The most powerful language in existence is probably common lisp. It allows you to use language to define new features of the language. Infinite cosmic power, pretty much.
It is also unusable for large teams because every programmer can and will come up with his own programming dialect that will be nigh-incomprehensible for everyone else.
That’s why for business production you’ll need language that restricts your creativity so the people in the team won’t get too creative by making their code hard to read. That’s why we have python that put those restrictions to eleven, by enforcing formatting, that’s why C# will stubbornly peresist in its attempt to babysit you, that’s why java is bureaucratic, and that’s why anybody who uses C++ will have some coding standard enforced (and sometimes that standard will avoid fundamental features of the language).
There are two conflicting goals in language design:
First programmer will want maximum expressiveness and ability to quickly implement any convoluted idea in code.
However, company that employs programmer will want a language that can be used by brain-dead monkey. In order to cut hiring costs.
While language is a tool, not all languages are equal to each other. They have strength and weaknesses.
For example, prolog can solve graph coloring problem in 3 lines of code. However it can’t be used in same fashion as C++.
instead of trying to be “perfect programmer” (or some other nonsense like that), people should pick languages that complement them the best and are compatible with their mindset. C++ grants perfect control over the program and sense of stability when codebase grows - at the cost of significant complexity and longer training period. If that is not what you want, pick different tool.
