When is something language agnostic? Why is it called that way?
- Anybody can ask a question
- Anybody can answer
- The best answers are voted up and rise to the top
Language agnostic refers to aspects of programming that are independent of any specific programming language. At least, that's how I've heard it used for the last thirty years.
The world "agnostic" is derived from the ancient Greek for "don't know". So something which is "language agnostic" doesn't need to know about computer languages; it means the same thing as language independent. Things that would be language agnostic include algorithms, or Agile, or a runtime library with bindings to many languages.
Some Mac OS X features are not language agnostic, because they're really designed to be used from Objective C, can only be used with difficulty from C or C++, and don't even have bindings for many languages.
There can also be a subtext to using "language agnostic" rather than other terms.
In colloquial English, someone who says they're "agnostic" means they are neither religious nor an atheist: they "don't know" about God. This is usually verbal code for "I don't like to talk about religion, so don't try to convert me."
So sometimes when people talk about being "language agnostic", they're trying to stay out of arguments about what computer language is better.
When a solution is called "language-agnostic" you are literally saying that your solution "doesn't know about" languages, meaning its universal or independent from language specifics (paradigms, language idioms, etc).
For example, design patterns are language-agnostic, because the way they are described the specific implementation doesn't matter as long it sticks to the whole or a subset of the pattern (v.gr. some design patterns can be implemented without OOP).
UML is language-agnostic, BPMN is language-agnostic, ERM is language-agnostic. An algorithm in pseudo-code is language agnostic...
Anything that is meant to be programmed but not described in a specific language can be called language-agnostic.
I haven't heard the term before, however, I would assume it means learning aspects of programming that are independent of any specific programming language.
There are a lot of ads asking for "language agnostic programmers". They're looking for people who are okay with programming in whatever language is needed to get the work done. They want people who are totally fine with learning another language if that's what the project calls for.
They're looking for people who aren't clinging to just one language and are unwilling to program in anything else. It's a way of avoiding people who say things like, "Ugh, you should change your whole system over to XYZ language! If you don't you're dumb!" A lot of people make those comments in response to those ads without realizing the massive expensive of rewriting a large system in another language. Could you eek out a 1% performance increase by swapping languages? Yeah, sure, but most of the time it doesn't make sense for a company to focus on that. It's not worth the money.