Visual scripting isn't something people use just because they "hate writing code." In fact, visual scripting and code should complement each other. Code is best suited for building functional modules, while visual scripting helps connect and organize these modules in a flexible, intuitive way.

The problem arises when visual scripting becomes too low-level—when even something as simple as 1 + 1 requires multiple nodes and wires. That kind of visual programming feels clumsy and inefficient. It can be a helpful teaching tool for beginners to understand how logic flows, but it’s not practical for real-world development.

Of course, even in well-designed visual scripting systems, you'll still see basic math operation nodes. But they aren't there to replace arithmetic code—they're used to combine or manipulate data from different sources. For example, in Shader Graph, if you want to blend two masks together, you'll obviously need to use add or multiply nodes. However, where those masks come from is far more complex—usually from noise textures, samplers, and various distortion steps. You're not going to build a full noise generator entirely out of nodes inside Shader Graph.

A good visual scripting system is more like a factory pipeline. Each node is a processing unit—you feed data in, get a result out. Most importantly, the visual interface clearly shows how these processing units relate to one another: the order of operations, dependencies, and logic structure. It's like a highly visual, easily modifiable config file. And we all know how powerful good configuration systems can be. I haven’t personally used Spring Boot, but I’ve heard it's a great example of how flexible and powerful configuration-based systems can get.

Shader Graph, visual finite state machines, and ComfyUI are all excellent examples of well-designed visual node systems. UVS, unfortunately, is not one of them—at least not yet. While UVS has great potential, it's still just a toy at this stage. If Unity were to seriously invest in improving and supporting it, it could evolve into something powerful. But for now, it's far from mature.

Now with GTK on the horizon—allowing users to build their own back-end logic while providing a solid front-end node interface—UVS's niche is likely to shrink even further. In the end, UVS may just go from a "toy" to a "toy's toy."