←back to thread

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

(www.youtube.com)
296 points gyre007 | 1 comments | 17 Oct 19 10:10 UTC | HN request time: 0.213s | source
Show context
onion2k ◴[17 Oct 19 10:39 UTC] No.21280617[source]▶
JavaScript isn't a functional language itself, but you can use a functional library like lodash/fp (https://github.com/lodash/lodash/wiki/FP-Guide) on top of it to get all that lovely functional goodness in your frontend and node code. Using lodash/fp has made my frontend state management code a lot nicer, and I'm really only just starting out with it.
replies(4): >>21280640 #>>21280696 #>>21280761 #>>21281273 #
Borkdude ◴[17 Oct 19 10:44 UTC] No.21280640[source]▶
The video explains how JavaScript started out as a Scheme-dialect (Lisp) but for marketing reasons they chose a more Java-like syntax and adopted Java into the name.
replies(2): >>21280673 #>>21285383 #
galfarragem ◴[17 Oct 19 10:51 UTC] No.21280673[source]▶
An historical mistake that humanity is paying (and will pay) for a long time.

Scheme 'cloths' was a viable option. Lisp remains the most popular scripting language among Autocad users despite Autodesk pushing other languages (.NET and JS). So popular that Autocad clones use it also as a scripting language[1].

Edited [1] https://www.zwsoft.com/zwcad/features#Dynamic-Block

replies(2): >>21280708 #>>21280945 #
daliusd ◴[17 Oct 19 10:57 UTC] No.21280708[source]▶
I was working for bigest Autocad competitor for more than 10 years and never had to touch anything similar to lisp :)
replies(1): >>21281080 #
1. lisptw102019 ◴[17 Oct 19 12:01 UTC] No.21281080[source]▶
If my guess is right, that's because your company's product had their own proprietary language (MDL).

But, that was OK too, because if my guess is right, your company's product also had FAR FAR FAR better COM bindings than Autocad did for 99% of what you'd want to automate.