7 ms·
From what I've seen out of the Clojure community over the past few years, it seems like they're far more likely (and able) to offer up concrete examples of how
by aaronbrethorst 12y ago
From what I've seen out of the Clojure community over the past few years, it seems like they're far more likely (and able) to offer up concrete examples of how Clojure makes their businesses and products successful in a way that an imperative language could not. So, yay Clojure community, and boo on hand-wavy Lisp people.
e.g.:
http://www.kreuzwerker.de/en/blog/posts/why-clojure-rocks-2/ http://www.kreuzwerker.de/en/blog/posts/why-clojure-rocks-2/
https://news.ycombinator.com/item?id=5113060 https://news.ycombinator.com/item?id=5113060
- pjmlp 12y agoThat is also a sore point from the Lisp community in regard to Clojure. Clojure devs are willing to compromise a bit to allow a good integration within the JVM and other implementations, thus allowing some shops to buy into Clojure. Whereas many in the Common Lisp community will not, no matter what.
- deleted 12y ago[deleted]
- bad_user 12y agoWhat kind of compromises are you talking about? My impression (based on limited exposure) is that Common Lisp suffers from a lack of clear guidance on how to do things. It's common in Clojure for example to use immutable data-structures and in case of mutation to use atoms and STM. Compromising on issues is seen as reasonable, but not a best practice and often there's a clear path you can take for certain problems. It's an opinionated language without being obnoxious. To me the attitude exposed by Clojure (and Scala) is a breath of fresh air. Some people tend to focus on how pieces of code look, or on using certain abstractions and optimizations, forgetting that the most important thing for users is a working app. For example, surely things like TCO and continuations have value, but that value is being trumped by a huge ecosystem of libraries and tools that, while not beautiful, are decent.
- mark_l_watson 12y agoA long time ago, the inventor of the Clojure language Rich Hickey wrote a Java bridge for one Common Lisp implementation that was very good - I used it a lot for a while. So, Rich has been thinking of the practicalities of Java interop for a long time.
- _delirium 12y agoI don't see CLers as having a problem with JVM interop per se. ABCL is often recommended as a perfectly respectable implementation for people who need Lisp on the JVM. But it's true that Clojure and ABCL take different approaches to it.
- eudox 12y ago>Whereas many in the Common Lisp community will not, no matter what. Common Lisp on the JVM: http://abcl.org/ http://abcl.org/ Common Lisp/Java bridge: http://foil.sourceforge.net/ http://foil.sourceforge.net/
- pron 12y ago> ... in a way that an imperative language could not Perhaps a nitpick, but sometimes nomenclature is important. Clojure (like all Lisps) is an imperative programming language. "Imperative" languages are contrasted with "declarative" languages[1]. Where does functional fit in and what is the name for "non-functional"? Well, that's not clear, as "functional" (in the PL sense) doesn't even have an agreed upon definition. Is Clojure "functional", then? Well, it's certainly not pure like Haskell is (and it has explicit loops etc.), but it does encourage more uses of function composition than, say, Java, it's more declarative, and it also isn't object-oriented, but that doesn't make it not imperative. Actually, I think even Haskell still qualifies as imperative. But Clojure can certainly be contrasted with OO and procedural languages (even though at least one of its core abstractions -- protocols -- is borrowed from OO). [1]: http://en.wikipedia.org/wiki/Imperative_programming http://en.wikipedia.org/wiki/Imperative_programming
- andreasvc 12y agoI think declarative should be contrasted with procedural, not imperative. Also, your reference/footnote [1] is missing.
- wtetzner 12y agoActually, I would say that protocols are more influenced by Haskell type classes than OO interfaces.
- eru 12y ago> Actually, I think even Haskell still qualifies as imperative. How so?
- LesZedCB 12y agoTechnically, if a language can produce side effects, it's considered imperative. However, nobody really is going to say that Haskell is imperative.
- Tyr42 12y agoThough there are some claiming that Haskell is the best imperative language because of having to state upfront what effects each bit of code can have. Since evaluation order is not very straight forward in Haskell, effectful code has to be explicitly ordered, which makes is very clear.
- fnbr 12y agoI tried Clojure, and I quite like it as a language (especially the thread-first & thread-last macros [1, 2]). I don't, however, like the ecosystem surrounding it. I find Leiningen (while an excellent tool) far too heavy for the majority of my purposes. I much prefer other functional languages (e.g. OCaml, Haskell) that don't need such an intricate project structure. With OCaml & Haskell, I can start with one source file in one directory and gradually build up to a more sophisticated layout as needed, rather than have a complicated layout imposed upon me by the project. [1] http://clojuredocs.org/clojure_core/clojure.core/-%3E http://clojuredocs.org/clojure_core/clojure.core/-%3E [2] http://clojuredocs.org/clojure_core/clojure.core/-%3E%3E http://clojuredocs.org/clojure_core/clojure.core/-%3E%3E
- bad_user 12y agoYou can get started with Clojure without Leiningen. You can get started with Scala without SBT. These are build tools for serious projects, with lots of options and lots of things they do for you. Some people recommend them to beginners and while that's not necessarily wise, it goes to show that they are mature and OK enough that some beginners cope with it. Yes, you can get started easily with Haskell - but then Cabal is such a complete piece of shit that people felt the need for a Haskell distribution with batteries included. And it is my feeling that you're mixing the cause and the effect here.
- leishulang 12y agoI agree. If Cabal was as good as Leiningen, then Haskell would has been way more popular than today.
- pjmlp 12y agoAvoid success at all cost. :)
- leishulang 12y agoLeiningen prevents clojure from having the dependency hell problem from the beginning, which haskell was prone to but eventually fixed by sandboxing. Then would you say sandboxing is too heavy for haskell? Now if by heavy, you mean the folders structure lein generates, then I disagree. Those folders actually keep the task of understanding any lein project easy. If by heavy, you mean the JVM: You can compile the thing into a jar that runs on any jvm, or a js file using clojurescript. JVM, web browsers and Node.JS are very likable cross-platform layers, and I don't see why binary executable that are OS dependent compares.