News for hackers. Stuff that matters.
Re:Long Names are Long by vorg on Friday June 17, 2016 @04:34PM (#11925375)
> users.map {|u| "(" + u.first_name + ")" }

If you need to specify the "u" in order to re-use it in one place only, then your language is syntactically challenged. Use a better language instead of caring about the names. A more flexible language would enable a predefined name like "it" or "_" instead, e.g:

    users.map{"(" + it.first_name + ")"}
or even provide syntax to do common stuff, e.g. the asterix in:

    users*.{"(" + first_name + ")"}
Re:Long Names are Long by kazinator on Friday June 17, 2016 @05:05PM (#11925548)
In a tight scope like this, `u` is the same thing as the classic "dummy variable", like the `i` in a for loop. "For a user u, do this". Dummy variables must never be given long names, because long names say, "this is not a dummy variable", which is a lie in that case.
Re:Long Names are Long by GregBuchholz on Friday June 17, 2016 @05:04PM (#11925541)
Re:Long Names are Long by robwilliams on Friday June 17, 2016 @05:08PM (#11925565)
>Use a better language instead of caring about the names.

That's not always an option.

Also, I don't find the language OP linked syntactically challenged. C# has a similar syntax and it's much more readable than what you've provided:

people.Sort(p => p.FirstName);