xyz The intended purpose you cited (make aspects of game logic available to non-programmers on a team) really makes no one happy.
No one is happy? Really? Well, that quote mentioned that visual programming was used. Note the wording — "main engine language". How visual programming can be a main engine language is a mystery to me, but if reworded like "Was visual scripting used in your project?" — the result could be quite different. In any case — a certain proportion of developers used it.
And the reason they shy away from coding in the first place is precisely that they don't like or want to think like programmers.
The problem is mirrored. Programmers, for the most part, are not artists. That's why designers, looking at the design of games created by programmers for programmers, turn grey and lose the last vestiges of their hair. Any means of engaging artists to create games and furnish them with a comfortable atmosphere in this is justified.
Much better than forcing visual scripting down everyone's throat.
That's probably a viable option. But apparently each approach has its own niche. And why substitute concepts and use the term "forcing"? Choice is good; no choice is bad.
Otherwise, your game won't happen, regardless of how much visual scripting or other such gimmicks you throw at it.
Blueprint disagrees with you.
Personally, I've made a conclusion for myself and am trying to learn programming, but getting artists involved as much as possible is the main goal. And, of course, the question of how best to organize the joint work of characters so different mentally and in terms of experience, but very similar in terms of extreme individualism, is extremely relevant.
Godot is fundamentally different from all other engines in that it is ideal for learning programming.
For many of these users, Godot is a tool to learn programming instead.
Yup, GDScript is a simple and straightforward language. But, keeping it visually coded could help the student to learn, if the teacher could show the effect of the functions and variables. (Such a request has been made in this forum.) It could also help students learn how to work collaboratively. This is a niche where Godot has little competition. Today's students, introduced to programming through Godot, could participate in its development in the very near future. It's an investment — you don't forget your first love. And throwing away such a gold mine is, in my opinion, not very witty.
Designer vs. programmer
I haven't figured out how to embed a video and it's not showing up for me. That's why it's duplicated by a heavy .gif. If the video is visible, the gif can be removed to save space.
Przepraszam. Maybe I'm very paranoid, but I have the impression that the degree of discussion rises a little, so I'll leave it at this point.