Like your word processor is the English language, you mean? Like the hammer is the nail? You seem to have trouble with separation of concerns.
That's an invalid comparison. Computer programming languages are designed exclusively for the communication of instructions from a human to a computer. You can (if you want) write a piece of code on a bit of paper, but the main purpose of doing so (outside of the classroom) is to later input it into a computer so that the computer will do something. It's not for communication between humans, and the computer doesn't write responses to the programmer in the same language.
So we have something that is designed for communicating instructions to a computer, that is almost always authored in a computer-mediated environment. It seems a bit silly that the computer isn't interpreting the code as it is entered, and everything is delayed until the programmer hits "compile" (or just "enter" in REPL environment).
And then we build these IDEs that do syntax highlighting, parenthesis matching and block hiding/folding for us, and they're reinterpreting the code using a parse that may or may not match the language compiler/interpreter itself. It lets us make loads of silly little mistakes because it doesn't know enough about the language to spot when we've made a mistake.
So the IDEs get more sophisticated, and start trying to interpret scope and suggest valid identifiers when we start typing, but we still can't be 100% sure the computer isn't confusing two different things.
All this is because we have two separate mediations by the computer, programmed by different teams, instead of one; all this is because the IDE isn't the language. What I'm proposing is a language where the IDE is the language, but not a half-hearted attempt like Scratch which slows you down by taking your hands off the keyboard. Not one that restricts your choices to a screenful of drag-and-drop elements. One that gives you all the elements of the richest, most powerful languages used in professional and academic circles, but lays them out clearly and unambiguously, instead of hiding the semantics in an obscure string of #@! declarations.