You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In languages section, there are 3 different categories: command line interface (that is strange naming too), imperative and functional. The reason I am writing the issue is that, JavaScript is clearly imperative, not functional language. Like Java or Go. There are no Pattern Matching, Persistent Data Structures (at least yet, there's a ECMAScript proposal) and Algebraic Data Types.
Also in JavaScript if structure is a statement, not expression. That simply must be a imperative programming language. In functional languages if's are expressions.
Only functional features, that Javascript got at the present, are patterns like map or impure lambda expression alternatives called "arrow functions". Java got them too. They have really weak functional paradigmads.
Just move JavaScript to "imperative" section and don't change terms.
The text was updated successfully, but these errors were encountered:
InverMN
changed the title
JavaScript is NOT functional language
JavaScript is a NOT functional language
Sep 18, 2021
InverMN
changed the title
JavaScript is a NOT functional language
JavaScript is NOT a functional language
Sep 18, 2021
As i looked futher, I see more silly "mistakes". For example Elasticsearch is in "Tools" section. Yup, it is a tool, but more detailed is a database. Even more detailed, it's a Search Engine.
Also I don't understand why in general "Databases" category, there are two sections: "SQL" and "NoSQL". In that SPECIFIC case, I would prefer "Relational" and "Key-Value". I think databases should be categorized by paradigm, not query language. That kinds sucks.
That repo is very messy place about categorization. Newbies can get confused learning from here.
In languages section, there are 3 different categories: command line interface (that is strange naming too), imperative and functional. The reason I am writing the issue is that, JavaScript is clearly imperative, not functional language. Like Java or Go. There are no Pattern Matching, Persistent Data Structures (at least yet, there's a ECMAScript proposal) and Algebraic Data Types.
Also in JavaScript
if
structure is a statement, not expression. That simply must be a imperative programming language. In functional languagesif
's are expressions.Only functional features, that Javascript got at the present, are patterns like
map
or impure lambda expression alternatives called "arrow functions". Java got them too. They have really weak functional paradigmads.Just move JavaScript to "imperative" section and don't change terms.
The text was updated successfully, but these errors were encountered: