I find this attitude odd. No one is going to use node-based programming to build a CRUD-app backend. I think some non-game programmers feel threatened by ways of building behaviour that don’t need a computer science degree. The attitude in the games industry is necessarily the opposite. Programmers aren’t game designers or artists or puzzle designers and part of their role is to let those creative professions express themselves, which leads to a richer experience.
I hope software continues to empower creative expression in new ways like this and the barrier to entry keeps being lowered.
>I think some non-game programmers feel threatened by ways of building behaviour that don’t need a computer science degree.
I don't understand this motivation. Did they get the computer science degree only because they thought they needed credentials to be allowed to program? I mean, most of the clearly started programming during their college time but before they received their degree. Node based programming is done by beginners because learning a text based language just isn't a very strong barrier for anyone who is actually willing to invest the time. How long does it take to learn 50% of the most commonly used programming language syntax constructs? Maybe a month? Maybe less? Before you say that it's impossible to build a mental model that is useful for programming in one month, I am strictly talking about the interface to the computer (syntax/nodes). You still need the same mental model with a node based language.
I personally read a C book when I was a teenager and I basically grokked the syntax in the book in 7 days (not the entire language). The difficult parts were actually obtaining a mental model of things like pointers and how the heap and stack works, not which words or symbols to type to satisfy the compiler.
I think I was being too specific when I mentioned a computer science degree. What I wanted to convey is that these types of entry level, or “layperson” ways of specifying behaviour can seem threatening to those who have invested in a career in software development. Understanding pointers and memory management and compilation is often orthogonal to solving the problem at hand, unless the solution would benefit from such understanding (maybe due to performance or memory constraints, or a level of complexity that warrants it). This is, after all, why the industry has developed higher level ways of writing software, like scripting languages or higher level compiled languages. These tools let us trade off low level control for higher productivity. I think another axis of abstraction is in the UI of software development itself: trading away some of the ability to build arbitrarily complex systems in any domain in order to lower the barrier to entry.
I hope software continues to empower creative expression in new ways like this and the barrier to entry keeps being lowered.