>and anybody who can do that is going to get frustrated by guard rails and just want to do ‘real’ programming eventually. Sure, if there are guard rails. But i

>and anybody who can do that is going to get frustrated by guard rails and just want to do ‘real’ programming eventually. Sure, if there are guard rails. But ideally the environment available to them is the same environment (at least most of) the system itself is written in; it shouldn’t be dumbed down, just more approachable. >and the people that do, don’t need a more intuitive interface. We may not need it, but it sure does help. As a concrete example, I was using an Emacs media player interface a while back and was frustrated with how it responded to mouse clicks. Were it a different media player (even if it were free software) I likely would have just accepted it and moved on. But Emacs does this sort of end-user programming pretty well (once you’re over the learning curve of using Emacs itself) and I was able to quickly trace why it was behaving the way it did and patch the offending code.