3 ms·
Well, I have already agreed FP jobs aren't plenty :-) Business executives mostly prefer to stick to beaten paths, and it's understandable. I just don't see a tr
by kingofhdds 8y ago
Well, I have already agreed FP jobs aren't plenty :-) Business executives mostly prefer to stick to beaten paths, and it's understandable. I just don't see a tragedy here. OCaml was born in 1996, if I'm not mistaken, so it's a decade older than Clojure. Despite never reaching the industry mainstream, it never stopped being developed, it is used in real projects, so I guess we can agree it's very much alive. Clojure in my very subjective opinion is doing a bit better than that due to ability to augment software written in Java. So while I don't believe it will conquer the world anytime soon, I also believe it's not going to disappear anytime soon.
- ernst_klim 8y ago>Clojure in my very subjective opinion is doing a bit better than that due to ability to augment software written in Java. OCaml can embed or be embedded in native applications, but that's not the point. I think that the main problem with Clojure is the lack of types. Just look at how much Scala is more popular than Clojure, although it's also a strange functional language derived from OCaml/SML. There is a common opinion that types are a necessity, even ruby, racket and python are adding them. Clojure people are just trying to substitute types with a runtime evaluated contracts/Hoare triplets, which is not an adequate substitution.