Programming Languages - Current and Historical, Nemanja Cvejić
Programming Languages - Current and Historical, Nemanja Cvejić
LANGUAGES
Current and historical
• The description of a programming language is usually split into the two components
of syntax (form) and semantics (meaning).
1950s
o Autocode (1952): This family of “simplified coding systems” was created in the 1950s specifically for
use with the digital computers at the universities of Manchester, Cambridge and London. Considered
by many to be the first complied programming language ever invented, Autocode was developed by
Alick Glennie to be both comprehensible and high-level.
1960s
o Algol 68 (1968): Short for Algorithmic Language 1968, Algol 68 was an imperative programming
language designed as a successor to Algol 60. With a wider scope of application and rigorously defined
syntax, this language was the first to be fully defined before it was implemented.
PROGRAMMING LANGUAGES THEN AND NOW
1970s
o Pascal (1970): Named in honor of the French mathematician Blaise
Pascal, this programing language was developed by Niklaus Wirth.
Pascal enabled programmers to define their own complex datatypes and
made it easier to build dynamic and recursive data structures like lists,
trees and graphs.
Visual Basic .NET (2001): A successor to the original Visual Basic language, Visual Basic .NET
is a high-level programming language implemented on the .NET framework. It uses statements to
specify actions and is one of the two main languages targeting the .NET framework, along with
Visual C#.
2010s-Present
Swift (2014): Swift was created by Apple for iOS and OS C development. It was introduced in
2014 at Apple’s Worldwide Developers Conference. Designed to work with Apple’s Cocoa and
Cocoa Touch frameworks, Swift is meant to be more concise and resilient to erroneous code.
THE FUTURE OF PROGRAMMING LANGUAGES
Developers are moving away from managing physical servers to calling APIs that touch storage, computer,
and networking resources. In turn, developers are trying to automate everything as code through static
configurations, scripts, and files. Such automation would be easier if developers had programming
languages that matched the task at hand, but they don't. So, using a general purpose language like Java, a
developer might invest thousands of lines of code to try to express business logic and mostly fail. To solve
for this, we're seeing companies like HashiCorp (HCL) and oso (Polar) release special-purpose declarative
languages.
Even at the risk of programming language proliferation, this feels like the right way forward: Purpose-
built instead of general-purpose languages. However, we're likely to see many of these programming
languages rise and fall before we settle into a useful set of standard declarative languages.
THANK YOU FOR
YOUR ATTENTION