"Don't use 'i' because it occurs often in keywords, making it hard to search for" is the most outlandish thing I've head in a good several weeks, even without the Scrabble reference.
There's absolutely nothing wrong with single-letter variable names with miniscule scopes. (Well, never use lower-case 'l' for anything, but the rest are fine.)
So? They are different names and have different types. Maybe this is a ruby specific thing. Are you suggesting since "u" looks more different from "users" than "user", it's easier to tell it's a different type? Usually in non statically typed languages, I thought you make the variable more descriptive to make up for lack of types not less descriptive. For example:
user_collection.each { |user| puts user.name }
If I've got a bunch of little lambdas, short loops (under 10 lines, perhaps), or list comprehensions, I'm not going to use longer names in them, because the context is clear and limited in scope.
If the variable's got to stick around longer (like throughout a function/method), it'll get a more descriptive name. As the scope grows, the variable loses the context that it came from, and it's more likely to need a longer name to make its meaning clear.
On a separate matter: you should read the HN guidelines.
Irrelevant. This function is painfully short.
> small functions can grow
It's a microlambda passed to a map function. 99% of these will never grow past a single expression. Hell, 95% of these will never even be modified.
> consistency is better
What, exactly, is this inconsistent with?
> you should read the HN guidelines
There's a difference between being uncivil and expressing frustration frankly.
Irrelevant. Other functions are longer. And needless human minification will undoubtedly creep in there too.
> What, exactly, is this inconsistent with?
Other functions.
> expressing frustration frankly.
Calling someone a wanker isn't exactly a pinnacle of expression.
No, it's not. But you shouldn't confuse your own identity with your coding style preferences, which were what the comment used "wankery" to describe.
> multiplied by the amount of loops, is somewhat inconsiderate.
And using the more detailed variable name is misleading. It implies a longer scope, to me.
Until it isn't. How do you enforce this?
"Please use descriptive variables everywhere, except for when you are iterating over a list of users. Use "u" in that case. Thanks."
When the scope is limited to a single line lambda, "first letter of the thing it is" is plenty descriptive enough, especially given that it's a strong convention in ruby.
(In an example of the opposite extreme, I'm currently working int codebase where every non-function local/non-instance variable has to use its fully qualified path name. Extremely descriptive; extremely unreadable.)
The other direction is the same. If your team doesn't share a "common sense", then someone will end up writing value[axis_x][axis_y][axis_z], because single-letter names are prohibited.
Your own post provides good examples - you use "it" and "this" because, in context, they are clear and easier to write and read than a longer version.