You don’t actually need to know any of the functional programming languages to work in the AI sphere. Moreover, codebase in pure funcional languages is hard to understand and maintain, that’s why they are rarely used in production. Of course you can learn any language for funsies, but I’d recommend Kotlin as a modern hybrid OOP language with a solid functional toolkit
Moreover, codebase in pure funcional languages is hard to understand and maintain, that’s why they are rarely used in production.
hahahah how to trigger a lot of people working with these pure functional languages (like me).
I’ve worked with both “normal languages” like C++, java, Perl, javascript (node + UI), etc… and then I switched to Haskell and Clojure.
And our current production code is a LOT better than in traditional languages. In particular, maintenance is a lot cheaper that what I was used to when working with more traditional languages.
Regarding the community impact I would advise to use Clojure instead of Haskell (or Purescript, or Elm). Clojure is a nice middleground that has a huge advantage of being very stable (by that I mean, the code you write today will probably be very easy to deploy in 10, or 20 years from now).
Note however, the language alone is not sufficient to write good code, but it helps you choose better abstractions that will be easier to maintain. If you dive into the spirit of the language, you will have a better intuition and understanding about state management of big applications and will probably make more visible some design issues.
Moreover, codebase in pure funcional languages is hard to understand and maintain, that’s why they are rarely used in production.
This is incorrect. They are rarely used because procedural languages have momentum. It’s way more likely you’ll get Joe Codemonkey to learn and be productive quickly with functional features added to a procedural language than to learn and be productive quickly with an entirely different paradigm. So that’s what happens.
This is incorrect. Functional code bases exist in many production environments. Twitter (pre musk) migrated their bloated code base TO Scala because functional code bases are easier to maintain and understand.
If you think about it, it makes sense, side effect free code will be easier to maintain just due to the lack of side effects.
You don’t actually need to know any of the functional programming languages to work in the AI sphere. Moreover, codebase in pure funcional languages is hard to understand and maintain, that’s why they are rarely used in production. Of course you can learn any language for funsies, but I’d recommend Kotlin as a modern hybrid OOP language with a solid functional toolkit
hahahah how to trigger a lot of people working with these pure functional languages (like me).
I’ve worked with both “normal languages” like C++, java, Perl, javascript (node + UI), etc… and then I switched to Haskell and Clojure. And our current production code is a LOT better than in traditional languages. In particular, maintenance is a lot cheaper that what I was used to when working with more traditional languages.
Regarding the community impact I would advise to use Clojure instead of Haskell (or Purescript, or Elm). Clojure is a nice middleground that has a huge advantage of being very stable (by that I mean, the code you write today will probably be very easy to deploy in 10, or 20 years from now).
Note however, the language alone is not sufficient to write good code, but it helps you choose better abstractions that will be easier to maintain. If you dive into the spirit of the language, you will have a better intuition and understanding about state management of big applications and will probably make more visible some design issues.
This is incorrect. They are rarely used because procedural languages have momentum. It’s way more likely you’ll get Joe Codemonkey to learn and be productive quickly with functional features added to a procedural language than to learn and be productive quickly with an entirely different paradigm. So that’s what happens.
This is incorrect. Functional code bases exist in many production environments. Twitter (pre musk) migrated their bloated code base TO Scala because functional code bases are easier to maintain and understand.
If you think about it, it makes sense, side effect free code will be easier to maintain just due to the lack of side effects.