←back to thread

Why Isn't Functional Programming the Norm? [video]

(www.youtube.com)
296 points gyre007 | 6 comments | 17 Oct 19 10:10 UTC | HN request time: 0.837s | source | bottom
Show context
BrissyCoder ◴[17 Oct 19 11:33 UTC] No.21280905[source]▶
People at the places I work keep memeing links to blog posts along the lines of "OOP is dead. Functional programming is the new king".

Yet to see a single line of a functional language in production.

As other commenters have mentioned most decent modern lanuages are multi-paradigm.

replies(9): >>21280928 #>>21281029 #>>21281110 #>>21281306 #>>21281812 #>>21283526 #>>21285298 #>>21285583 #>>21286410 #
1. fheld ◴[17 Oct 19 11:38 UTC] No.21280928[source]▶
might be interesting for you, Lips in production:

https://tech.grammarly.com/blog/running-lisp-in-production

replies(3): >>21281359 #>>21281374 #>>21283583 #
2. juki ◴[17 Oct 19 12:37 UTC] No.21281359[source]▶
Notice that they are using Common Lisp, which is a multi-paradigm language, rather than a more functional lisp like Clojure.
replies(1): >>21281654 #
3. capdeck ◴[17 Oct 19 12:39 UTC] No.21281374[source]▶
I used to work in a company that had part of the process written in Lisp and it was in true production. Once the (fp) guy left the company everyone else had to support that code. What a nightmare that was. No one wanted to touch it with a ten foot pole. Should we had another FP guru in our midst, that may have turned out differently. But everyone was in agreement that that part needs to be rewritten in a language that everyone else is using. In real life - if most stuff in your company is FP and there is plenty of expertise to go around - do FP. If not - do not. :-)
replies(1): >>21282127 #
4. TurboHaskal ◴[17 Oct 19 13:14 UTC] No.21281654[source]▶
They also use Clojure at Grammarly AFAIK.
5. Qwertystop ◴[17 Oct 19 14:02 UTC] No.21282127[source]▶
Arguably, if you knew that A: there was code in Lisp and B: only one person knew how to support it, they should have either rewritten it while the one who understood it was still there, or had more people learn Lisp, or hired more people who knew Lisp. It shouldn't have been allowed to reach the point where someone quit without anyone else having a clue.
6. Grue3 ◴[17 Oct 19 16:17 UTC] No.21283583[source]▶
Common Lisp is a great language for OOP programming though. Almost any serious CL code heavily uses CLOS.