Easily comprehensible code? Hard boundaries, and the ability to figure out what the code does without having to mentally step through it? Perhaps you can even c

Easily comprehensible code? Hard boundaries, and the ability to figure out what the code does without having to mentally step through it? Perhaps you can even click a button when the cursor is on an identifier, and be taken to the definition of the entity of that name, or the small subset of possible entities of that name that this identifier could refer to? Possibly the computer could check your work without your even having to run it, and actually prove that certain types of error cannot possible occur? That actually sounds really helpful and I'm not sure why people don't embrace it. (One point you do make that is quite correct is that static typing is helpful for novices. And yet so many languages designed for beginners' use try to make things "easier" by turning typos into new variables, letting variables switch type, and generally poking their user in the eye. Never figured this one out - though I suppose this is good training for the novice programmer, because programming is such a straightforward activity and without having the language itself to keep them on their toes they might find it insufficiently exacting, not demanding enough, and requiring basically nothing in the form of concentration, thought and precision.)