|
|
|
|
|
by justinjlynn
906 days ago
|
|
What's wrong with that? They are. We can always make the finer distinction of "Von Neumann architecture inspired digital electronic computer" if you wish to exclude the examples you've given. After all, anything which transforms a particular input to a particular output in a consistent fashion could be considered a computer which implements a particular function. I would say - don't confuse the word's meaning with the object's function and simply choose a context in which a word refers to a particular meaning, adapt to others contexts and translate, and simply deal with the fact that there is no firm division between computer and not-computer out in the word somewhere apart from people and their context-rich communications. If the context in which you're operating with an interlocutor is clear enough for you to jump to a correction of usage ... simply don't; beyond verifying your translation is correct, of course. As you're already doing this - likely without realising it - by taking care in doing so consciously you're likely to find your communications more efficient, congenial, and illuminating than they otherwise would be. |
|
By doing so, you get to make a point—perhaps via analogy, perhaps via precision, perhaps via pedantry—which is illuminating for you but now confusing for your reader. And to explain yourself, you must swim upstream and redefine a term while simultaneously making a different point altogether.
Much has been written about jargon, but a primary benefit of jargon is the chance to create a domain-specific meaning without the baggage of dictionary-correct associations. It’s also why geeks can be bores at dinner parties.