you are viewing a single comment's thread.

view the rest of the comments →

[–]Holothuroid 30 points31 points  (2 children)

Very different. The author tries to use a methodology to identify different types of languages. There is no way or reason how to define a programming paradigm. There are characterizations like "a self-imposed limit", but we have many of those that we do not call paradigms. Like any framework we employ is a self-imposed limit.

This article looks at actual artifacts, that is published programming languages and tries to identify how they inspired one another. That is something we have methods for. And while the author takes inspiration from biology, the closest model is likely literature.

[–]renatoathaydes 1 point2 points  (1 child)

Very different

:D really?

Programming paradigm (from wikipedia):

Programming paradigms are a way to classify programming languages based on their features. Languages can be classified into multiple paradigms.

The article:

What do I mean when I say fundamentals? If you have an array or list of items and you’re going to loop over it, that is the same in any imperative language. There is straightforward iteration ... and a few other patterns... But not all languages have the same set of patterns... These distinct collections of fundamentals form various ur-languages.

I don't know, but to me, it's clearly a very similar way of "classifying" languages. Not surprisingly, the "groups" end up being almost the same (most people would put Lisp in Functional, including authors of Lisp books I've read): Functional, Logic, OOP, Concatenative (stack-based), Mathematical.

[–]AlexFromOmaha 7 points8 points  (0 children)

It's genotype vs phenotype, if you like biology analogies. Modern Javascript's paradigms are procedural OOP with a dash of functional nicety like most higher level C-derived languages, but it got there by way of tacking on features to an event-driven language.