Languages I want to write
One with no errors. There's no concept of a "syntax error" or a "compiler error" or a function error. One of the most common things we joke about is people not reading error messages.<p>Whatever the design is, it would not ever spit a big red blob in your face which makes you wince and feel bad, nor would it fill your terminal - the place where you work - with screen after screen of tracebacks. It is unthinkable that you could write "x-1 = x+1" on a piece of paper and the equation scribbles on your workplace and you can't use it anymore.<p>There would be no adversarial relationship, you wouldn't be "fighting" the compiler or the borrow checker, no red squiggly underlines in an IDE. The whole approach would be reframed into the computer being a mechanical assistant helping you solve problems and guiding you <i>towards success</i> instead of slapping you.<p>A tuning fork plays a tone you can use to tune a piano string. It doesn't slap you if tweak the string tuning the wrong way. An archery target lets you see when you miss the centre, it doesn't also shout at you. Code <i>not working</i> is feedback all by itself. The tools shouldn't add negative feedback to that, they should guide towards where working is.