Combine l10n js files of one language

[MorrisJobke]

• currently 10% of all requests (13 out of 126 requests in the files app) are l10n files
• we should combine all l10n files of a language of all enabled apps (this doesn't change that often)
• maybe use the [PoC] JS Combiner #3988

cc @rullzer @ChristophWurst @nickvergessen Does this sound good?

[ChristophWurst]

* we should combine all l10n files of a language of all enabled apps (this doesn't change that often)

so … ?

[MorrisJobke]

so … ?

... somebody should do it™

[ShGKme]

• we should combine all l10n files of a language of all enabled apps (this doesn't change that often)

Would it mean, we always load localization for all the apps, even on a page with only some apps?
Even on the login page / login flow?

[nickvergessen]

Even on the login page / login flow?

That will not work, as we can not load apps that are restricted.
But I guess the main idea would be heavy caching so while we load all apps, we try to only do so once?

[ShGKme]

We can cache HTTP request, but not the translation registration.

My fear is that we can:

1. Win in:
   • Number of HTTP requests (not supposed to be a problem except HTTP/1.1 setups)
   • Opening a second app (translation is already in the cache)
2. Lose in:
   • Freezing time on EVERY page init (due to a large localization registration)
   • Opening Nextcloud for the first time (important for guests and small pages like public share)

So I'd start with measuring translation registration to see if we win more than we lose.