9 ms·

I kind of understand for i18n, but not for most other things

• jorisw 2mo ago
  What could be the possible benefit of collapsing 'internationalization' to "i18n"? Which scarce resource (time? space?) was saved, in what context? For example, I'll take "react-internationalization" over "react-i18n" for a package name any day. Why obscure anything unless a clear problem was solved doing it, that warrants the ambiguity?