Skip to content

Comment on Acronym Fatigue Series Introduction: why I'm wary of acronymsparent

Comments

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?

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.