Blogs >> Education & Books >>
Comparison of various programming languages
Hey folks, I recently researched about various Programming Languages.
Here I m going to discuss certain attributes of each language.
Basic
Year Introduced: 1964
Paradigm: Imperative, Procedural
Standardization: Yes, ANSI, ISO
Type Strength: Varies by dialect
Intended Use: Application, Education
C
Year Introduced: 1972
Paradigm: Imperative
Standardization: Yes, ANSI C89, ISO C90/C99
Type Strength: Weak
Intended Use: System
C++
Year Introduced: 1979
Paradigm: Imperative, Procedural, Object-oriented, Generic
Standardization: Yes, ISO
Type Strength: Strong
Intended Use: Application, System
C#
Year Introduced: 2000
Paradigm: Imperative, Object-oriented, Functional, Generic, Reflective
Standardization: Yes, ECMA, ISO
Type Strength: Strong
Intended Use: Application, Web
Haskell
Year Introduced: 1990
Paradigm: Functional, Generic, Lazy evaluation
Standardization: Yes, Haskell 98
Type Strength: Strong
Intended Use: Application
Java
Year Introduced: 1995
Paradigm: Imperative, Object-oriented, Generic, Reflective
Standardization: No
Type Strength: Strong
Intended Use: Application, Web
Perl
Year Introduced: 1987
Paradigm: Imperative, Procedural, Reflective, Functional, Object-oriented, Generic
Standardization: No
Type Strength: Weak
Intended Use: Application, Text processing, Scripting, Web
PHP
Year Introduced: 1995
Paradigm: Imperative, Procedural, Object-oriented, Reflective
Standardization: No
Type Strength: Weak
Intended Use: Web, Server-side
Python
Year Introduced: 1989
Paradigm: Imperative, Object-oriented, Functional, Aspect-oriented, Reflective
Standardization: No
Type Strength: Strong
Intended Use: Application, Scripting, Web
Scala
Year Introduced: 2003
Paradigm: Object-oriented, Functional, Generic, Lazy evaluation, Imperative
Standardization: No
Type Strength: Strong
Intended Use: Application, distributed computing
Basic
Year Introduced: 1964
Paradigm: Imperative, Procedural
Standardization: Yes, ANSI, ISO
Type Strength: Varies by dialect
Intended Use: Application, Education
C
Year Introduced: 1972
Paradigm: Imperative
Standardization: Yes, ANSI C89, ISO C90/C99
Type Strength: Weak
Intended Use: System
C++
Year Introduced: 1979
Paradigm: Imperative, Procedural, Object-oriented, Generic
Standardization: Yes, ISO
Type Strength: Strong
Intended Use: Application, System
C#
Year Introduced: 2000
Paradigm: Imperative, Object-oriented, Functional, Generic, Reflective
Standardization: Yes, ECMA, ISO
Type Strength: Strong
Intended Use: Application, Web
Haskell
Year Introduced: 1990
Paradigm: Functional, Generic, Lazy evaluation
Standardization: Yes, Haskell 98
Type Strength: Strong
Intended Use: Application
Java
Year Introduced: 1995
Paradigm: Imperative, Object-oriented, Generic, Reflective
Standardization: No
Type Strength: Strong
Intended Use: Application, Web
Perl
Year Introduced: 1987
Paradigm: Imperative, Procedural, Reflective, Functional, Object-oriented, Generic
Standardization: No
Type Strength: Weak
Intended Use: Application, Text processing, Scripting, Web
PHP
Year Introduced: 1995
Paradigm: Imperative, Procedural, Object-oriented, Reflective
Standardization: No
Type Strength: Weak
Intended Use: Web, Server-side
Python
Year Introduced: 1989
Paradigm: Imperative, Object-oriented, Functional, Aspect-oriented, Reflective
Standardization: No
Type Strength: Strong
Intended Use: Application, Scripting, Web
Scala
Year Introduced: 2003
Paradigm: Object-oriented, Functional, Generic, Lazy evaluation, Imperative
Standardization: No
Type Strength: Strong
Intended Use: Application, distributed computing
* * * * *
|
|
