Problem
The filter named "Current user's language" is very misleading. Those who know the language system in Drupal core would assume this filter will apply the language preference of the user which is not at all the case. It takes the content language negotiated for the page, which may or may not be the user's preferred language in their setting. So the language used is not from the user profile but determined dynamically for the page (and may depend on URL components, session values, etc.
This is especially misleading since now for most entity types, you have a settings page that lets you default new instances of that entity type to a specific language. It has dynamic options like "Site default language", "Current interface language", "Author's preferred language". The author's preferred language actually means the language of the user authoring the entity there, unlike in views, where the user's language may or may not be the user's preferred language.
Proposed resolution
Figure out a better label for this.
Rename this filter to that.
If we also want specific user focused filter, we can add one for that too. May be a followup though.
