Jump to content

Language-agnostic: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
m cleared blanks
m clean up, typo(s) fixed: etc) → etc.) using AWB
Line 5: Line 5:
== Language agnostic ==
== Language agnostic ==


"Language agnostic" describes 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" describes 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 Java development team might choose to use Ruby or Perl for some development work, when Ruby or Perl would be more appropriate than Java.
For example, a Java development team might choose to use Ruby or Perl for some development work, when Ruby or Perl would be more appropriate than Java.
Line 21: Line 20:
*[[Language binding]]
*[[Language binding]]
*[[Middleware]]
*[[Middleware]]

{{disambiguation}}
{{disambiguation}}

Revision as of 07:16, 19 October 2015

Language-agnostic, language-neutral, language-independent, or cross-language may refer to:

Language agnostic

"Language agnostic" describes 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 Java development team might choose to use Ruby or Perl for some development work, when Ruby or Perl would be more appropriate than Java.

Computing

See also