Hacker News new | ask | show | jobs
by zjp 22 days ago
Acronyms I can handle. What I've always hated is aNz style compressions. a11y, a16z, stuff that you can't even guess at a decoding unless you know it already.
5 comments

My screen reader says "eleven why" for a11y. I hope that's fine with everyone
I don't have to guess because I'm smart enough to look things up.

P.S. The response is a ridiculous non sequitur -- I didn't say anything either for or against such terms, just that their meaning can be discerned.

But I would note that all of language requires all readers to be familiar with terms and their meanings. And specifically, if people aren't familiar with the notion of language-independent code then they aren't likely to understand what "internationalization" refers to, and if they are familiar with the topic then they almost certainly know what i18n means ... and the time and effort that it took to learn it is infinitesimal relative to all the other language and meanings that they have acquired.

Further, the whole argument from this person is intellectually dishonest nonsense. They claim that terms like HTTP and NASA are "at the expense of the reader", which is simply false. I and most other readers would far prefer to see these acronyms and initialisms than to have them spelled out every time. (And it would be a disaster if http were spelled out in URLs -- and it would be a disservice to the reader to spell that out.)

Yes, let's have each reader spend time and energy all day looking up abbreviations/acronyms/initialisms, so that the single writer can spend a little less time and energy in getting their own point across.
You know it never occurred to me I could look things up before. Everything I've ever known I learned orally. Even C. I remember sitting on pappy's lap, watching him wave his hand to draw out an asterisk in the air. "A pointer..."

Literary culture is so confusing.

Anyway, the editorial rule is to spell it out on the first use and then to abbreviate it:

The National Aeronautics and Space Administration (NASA) announced today... ...NASA says...

Many articles fail to do this and assume insider knowledge. It's all fine and good after you look it up or if you're an expert and familiar with the topic. Good for you. For everyone else, in other disciplines, or lay people, or for students, it's nice to extend the courtesy of spelling it out once.

I kind of understand for i18n, but not for most other things
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?

Imagine if Germans had invented this style. Great compressibility, but good luck dealing with a65z.
Yep, I've always thought they were f5g s4d.

Although that would make a cool number plate. Someone called Kate should get k8s c4r as her number plate. It would be an accurate description and also s4dly confusing.

If you don't understand anything I've written, you can catch my technical sales pitches here: https://t7ls3sp5s.com