There already is a visual scripting environment--its called LabView and its terrible.  LabView is used mostly by scientists who want to control their experiments but don't want to learn how to program.  It's very effective when dealing with hardware and you just want to get it working.  But if it doesn't work, you're screwed because its very difficult to debug.<p>That's actually the problem I forsee with the visual scripting environment.  There is no better single point of instruction than a compiler error or syntax error highlighting.  If you try to circumvent that process to make it more "accessible" to the public, you're going to keep your visual programmers in the dark as to what is actually occurring.