I don't think QWERTY is actually harming language design - designers simply implement multiple-character operators (like ==). (however, I certainly agree it's a

I don't think QWERTY is actually harming language design - designers simply implement multiple-character operators (like ==). (however, I certainly agree it's awkward and extended symbol operators would be cleaner). Also, as the author mentioned, I don't think it's really feasible to get all coders to agree on one 'coder keyboard' layout (hell - we've had 50 years to decide on an optimal editor and are no closer than when we started). I think the best solution is to continue with this multi-char symbol syntax, but to have keyboards with programmable centrally placed macro keys that can be automatically redefined by the current application. For example, when coding lisp I'd love to have dedicated paren keys, and maybe even a dedicated 'setf', 'defun', and 'let' keys. I think that as OLED keyboards ala the Optimus Maximus become more economically feasible and widespread over the next decade or two, this is exactly what will happen. Then, in 20-30 years when these keyboards become ubiquitous, language designers will start to implement non-ascii operators that can be mapped to the programmable keys. It will certainly be prettier - but I don't think it will herald in a new era of better languages.