Dvorak. I know 5 people, including myself, that switched to Dvorak and none of us regretted it or switched back.
It's not about speed, at least for me, but reducing stress on fingers and prevent inflammation and RSI.
Touch-typing comes easier with Dvorak. Even better if you use a Dvorak layout on a querty keyboard: there's no point in looking at the keys and this is also good for back/neck posture.
Please ignore all the people who insist on using qwerty without having had at least a year of Dvorak use experience.
You can write ClassesLikePython and variables_like_python in Nim.
Sometimes people end up having dangerously similar variable names in the same scope, e.g. username and user_name, where an incorrect tab-completion might introduce a bug.
Nim would require the developer to choose better names.
> This looks like an enjoyable source for weird bugs
It's meant to prevent them: in Python applications it's not uncommon to see bugs introduced by an incorrect completion, e.g. updatePlayerstatus / updatePlayerStatus / update_player_status
With case/underscore insensitivity you know in advance that there can be only one "updateplayerstatus" in your codebase and write it according to your style, e.g. always update_player_status
> The fundamental fallacy is the idea that tobacco is so dangerous that it, and anything comparably dangerous, must be banned.
Please name a country where selling or buying cigarettes is not legal.
> But you, I and everyone else on earth will die sometime, of something: whether it's cancer, congestive heart failure or something else entirely, we all die.
Strawman. By that logic we would not use safety belts or cars.
What is the experience for visually-impaired users that need high contrast UIs or braille terminals?