Hey.
Think about making english not the main language…
A lot of i18n are based on default language for example English…

But most of the time we are not translating an article, but we are translating a GUI.

And who said the translation of the GUI supposed to be exactly same structure and words like in the original language…
Let's suppose the text copyright should completely different in the point of view of the marketing of the product for every country or language. So its not a ‘translation’ but should be more of a named placeholder instead and just making different text for every language.

And another point. In updating every GUI language to a localized version, sometimes the update of a simple text copyrighting in the original language and marketing thinking in the main default language makes the translators translate the change from the original language to the derived language.
But! We do not want to make a new translation event, only a copyrighting text change in the main language without affecting sub translation, so why should the translation be even dependent on the main text?
So from the project management point of view its kinda not smart to make all the translations, dependent on some main language or some main text. we are not translating an article.

What do you say guys about that?