I forget about this post and conversation was retaken here:
In this new post the starting point was an issue with primary_language, but ends with similar arguments than I exposed here.
Just to be clear about my argument: Most of the multilanguage journals don’t require i18n in user’s names, so the feature request is “why not making this optional”?
Nate, sorry to persist with this, but in our service this is becoming a major usability issue.