Comment on Ask HN: What would you call a package whose purpose is to import data?Comments−andsoitis8moimports, ingest, dataimport, ímport, impørt.a few good principles (not rules) for naming libraries:a) signal abstraction levelb) avoid being too literal for it constrains evolutionc) pronounceable and spellabled) prefer nouns over verbs because libraries are things not actionse) metaphors beat descriptionsConsequently, I would avoid imports, ímport, impørt"Ingest" feels like it is in a good direction. Any good reason not to use it?−ctc24OP8moAgreed, I like `ingest` as well. It does somewhat violate principle d), but the other solutions violate more of those. And to your point, they're principles, not rules.−scaredreally8moHow about `importer`?
Comments
a few good principles (not rules) for naming libraries:
a) signal abstraction level
b) avoid being too literal for it constrains evolution
c) pronounceable and spellable
d) prefer nouns over verbs because libraries are things not actions
e) metaphors beat descriptions
Consequently, I would avoid imports, ímport, impørt
"Ingest" feels like it is in a good direction. Any good reason not to use it?
Agreed, I like `ingest` as well. It does somewhat violate principle d), but the other solutions violate more of those. And to your point, they're principles, not rules.
How about `importer`?