4 ms·
I'm dislike the not-so-recent trend of companies/projects/libraries that co-opt common words as their name. "Rust" and "elm" and "iced" wouldn't normally have a
by qwertygnu 5y ago
I'm dislike the not-so-recent trend of companies/projects/libraries that co-opt common words as their name. "Rust" and "elm" and "iced" wouldn't normally have anything to do with computing, but it still feels like a small intrusion on our language.
- ryanianian 5y ago> it still feels like a small intrusion on our language. All languages evolve over time, despite official bodies trying to reject foreign influence. (IIRC the French government has a department that tries to limit loan words from other languages, but good luck with that given the internet.) So what's the actual problem with it? Only downside I see is google-ability and occasional conflicts when two projects use the same name. Both of those exist with any naming Scheme (ha!) and imho haven't really ended badly for projects or their users.
- alpaca128 5y agoYou mean like Apple, BASIC, Lisp, Explorer, Safari, Chrome, Android, ...? This practice has existed from the start and I don't see it as an intrusion into the language. We humans are able to consider context (which is necessary for language either way), and that mostly takes care of it. When someone says "I've got rust on my PC's power supply" or "my python escaped" it's still very obvious it's not the programming language. And an outsider might have trouble following the conversation, but that would happen no matter what words are used. Whether we say "Elm" or "C++", the target audience knows what's meant and others wouldn't be able to follow either way.