Language-agnostic: Difference between revisions
heading |
bare url |
||
| Line 3: | Line 3: | ||
{{cleanup|reason = Describe more possible meanings of the terms "language-agnostic", "language-neutral", etc.; also discuss whether there is a distinction between the meanings of each phrase|date=October 2012}} |
{{cleanup|reason = Describe more possible meanings of the terms "language-agnostic", "language-neutral", etc.; also discuss whether there is a distinction between the meanings of each phrase|date=October 2012}} |
||
{{One source|date=February 2018}} |
{{One source|date=February 2018}} |
||
{{Bare URL|date=February 2018}} |
|||
}} |
}} |
||
'''Language-agnostic''' programming or scripting (also called '''language-neutral''', '''language-independent''', or '''cross-language''') is a software development paradigm where a particular language is chosen because of its appropriateness for a particular task (taking into consideration all factors, including ecosystem, developer skill-sets, performance, etc.), and not purely because of the skill-set available within a development team. |
'''Language-agnostic''' programming or scripting (also called '''language-neutral''', '''language-independent''', or '''cross-language''') is a software development paradigm where a particular language is chosen because of its appropriateness for a particular task (taking into consideration all factors, including ecosystem, developer skill-sets, performance, etc.), and not purely because of the skill-set available within a development team. |
||
Revision as of 03:55, 19 February 2018
 | This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)
|
Language-agnostic programming or scripting (also called language-neutral, language-independent, or cross-language) is a software development paradigm where a particular language is chosen because of its appropriateness for a particular task (taking into consideration all factors, including ecosystem, developer skill-sets, performance, etc.), and not purely because of the skill-set available within a development team.
For example, a language agnostic Java development team might choose to use Ruby or Perl for some development work, where Ruby or Perl would be more appropriate than Java.
"Cross-Language" in programming and scripting describes a program in which two or more languages must be implemented into the program code alongside the core programming language chosen to write the program. Whether this means including a script as a source, to be used when needed, running code within Language-Independent Virtual Machines such as JVM, or Object Models such as COM to cooperate with each other, or choosing languages that work well together natively.[1]
Related terms
- Language-independent specification
- Cross-language information retrieval, referring to natural languages, not programming languages
- Language independent datatypes
See also
- Bilingual (disambiguation)
- Language-independent (disambiguation)
- Glue language
- Language binding
- Middleware
- Polyglot (computing)