I've helped teach CS to high schoolers for a few years. In some years, we've used visual systems like this. In my experience, they help kids get started with programming really easily. They can slowly learn more and more programming concepts with immediate visual feedback. But, in all classes, they get stuck in learning to abstract or plan solutions ahead of time for more complex problems. That's a hard jump with every method of teaching CS, though. In a sense, the immediacy of visual programming can make it hard for them to slowly develop long-range planning and reasoning skills. I'm not sure if a purely symbolic approach is better, still. I do think a bit more practice-oriented learning may help - think multiplication table worksheets.
Cool video: https://youtu.be/D-guBA1_T_Y
It was quite baffling then, till, say start of my undergrad (age 18), on what was the point of learning to control a turtle using simple commands. It hit me finally, as I was trying to learn actual programming.
A lot of people (in my circles) say that learning to program is intuitive, easy. I have never believed that. To teach something like HTML/CSS/How to use MS Word etc would be far, far worse experience (I'm looking at you, second tier Indian schools) than learning to move a turtle using simple commands. If nothing else, it brings home the idea of moving commands to actuate things on the computer.
PS: I suppose you can make the argument that this is also accomplished by video games but I hold that syntactically coherent commands (LT 90; FD 10) give a better insight into command-action nature of interaction than (Up arrow; Up arrow; move mouse to enemy; left click).