Hacker News new | ask | show | jobs
by throwaway290 298 days ago
It's technical jargon in different industries, but it's still jargon, ie. words NOT self explanatory by their normal definitions in mainstream use. Other examples of such terms: "variable", "class"

For the same reason, "allow-list" list is not jargon, just like "component" or "extension"

To me there is one issue only: two syllables vs one (not a problem with block vs black for example but a problem with allow vs white) and that's about it.
1 comments
JumpCrisscross 298 days ago
> "allow-list" list is not jargon

Of course it is. If I tell someone to allow list a group of people for an event, that requires further explanation. It’s not self explanatory because it’s non-standard.

> just like "component" or "extension"

If you use them the way they are commonly used, yes. If you repurpose them into a neologism, no. (Most non-acronym jargon involves repurposing common words for a specific context. Glass cockpit. Repo. Server.)

link
throwaway290 298 days ago
If you tell your friend to put somebody on an allow-list and that requires further explanation, I think the problem is not the term but your friend, sorry...

Server, cockpit those are jargon. Allow and deny just aren't. Whatever.

link