Jump to content

Language-agnostic: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
m Reverted edits by Buchi Chidubem (talk) to last version by Minorax
Tags: Removed redirect Rollback Disambiguation links added
m Added links
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
{{Multiple issues|
{{factual accuracy|date=March 2013}}
{{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}}
}}
'''Language-agnostic''' programming or scripting (also called '''language-neutral''', '''language-independent''', or '''cross-language''') is a software paradigm in which no particular language is promoted.
'''Language-agnostic''' programming or scripting (also called '''language-neutral''', '''language-independent''', or '''cross-language''') is a software paradigm in which no particular language is promoted.


Line 11: Line 6:


As a development methodology, the concept suggests that a particular language should be 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.
As a development methodology, the concept suggests that a particular language should be 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.
For example, a language agnostic [[Java_(programming_language)|Java]] development team might choose to use [[Ruby_(programming_language)|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 are used to good effect within a program's code, with each contributing its distinctive benefits.<ref>{{cite web|url=http://queue.acm.org/detail.cfm?id=2543971|title=The Challenge of Cross-language Interoperability - ACM Queue|website=queue.acm.org}}</ref>
"Cross-Language" in programming and scripting describes a program in which two or more languages are used to good effect within a program's code, with each contributing its distinctive benefits.<ref>{{cite web|url=http://queue.acm.org/detail.cfm?id=2543971|title=The Challenge of Cross-language Interoperability - ACM Queue|website=queue.acm.org}}</ref>

Latest revision as of 13:42, 14 June 2023

Language-agnostic programming or scripting (also called language-neutral, language-independent, or cross-language) is a software paradigm in which no particular language is promoted.

In introductory instruction, the term refers to teaching principles rather than language features.[1] For example, a textbook such as Structure and Interpretation of Computer Programs is really a language-agnostic book about programming, and is not about programming in Scheme, per se.

As a development methodology, the concept suggests that a particular language should be 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 are used to good effect within a program's code, with each contributing its distinctive benefits.[2]

[edit]

See also

[edit]

References

[edit]
  1. ^ "Free Programming Books By Subject / Programming". EbookFoundation.
  2. ^ "The Challenge of Cross-language Interoperability - ACM Queue". queue.acm.org.