4 ms·
For me, the real game changer is the REPL-driven workflow you get with both Clojure and ClojureScript, but it's really hard to describe the details of how it's
by diggan 6y ago
For me, the real game changer is the REPL-driven workflow you get with both Clojure and ClojureScript, but it's really hard to describe the details of how it's different than hot-reloading in the React ecosystem. I've tried many times, but my explanations seems to mostly confuse people rather than enlighten them.
So let's use the words of others instead, here is the best explanation I know about why the Clojure REPL rocks: https://vvvvalvalval.github.io/posts/what-makes-a-good-repl.html https://vvvvalvalval.github.io/posts/what-makes-a-good-repl....
Short version is: you can send snippets of code to your REPL from your editor, and because of the common structure of Clojure apps, you can usually evaluate content in the middle of a function without having to change any code. Basically unlimited introspection into a running program.
I used to program in PHP, C#, Golang, Ruby, NodeJS/JavaScript (both backend/frontend) and some others, and no language comes close to the dev experience of Clojure. I'm sure other lisps are similar as well, but haven't used anything else than Clojure substantially.
- holtalanm 6y agoI went down the Clojure path once and wasn't nearly as impressed as you were, apparently.
- diggan 6y agoDid you actively get into the REPL workflow? If you didn't, I don't think you took properly advantage of what the language offers. Bit like using TypeScript and using `any` everywhere. If you did get into the REPL workflow, was it not helping you be more productive? Any showstoppers?
- holtalanm 6y agoMy complaints more reside with issues I ran into with the language itself. Mainly, meaningless exception messages and insane stack traces and poor tooling within my editor of choice (at the time). Also, I take issue with a language that touts itself as purely functional, but then builds itself off of the JVM, forcing you to use objects under the hood. You end up with some kind of weird FP/OO Frankenstein's monster that isn't _really_ FP, but also isn't _really_ OO. Also, since it is on the JVM, there is _no way_ you can actually have truly immutable objects or data structures, as much as Clojure likes to think that is the case. It places a lot of trust on the libraries that make up your program not to go into reflection and do some really annoying mutations. If that is the case, I'd rather just use something like Erlang or Haskell which are _truly_ functional languages, not just an OO system masquerading as a functional language. I _really_ like the syntax of lisp, and Clojure provides some really good extensions of that syntax with the way they do parameters, but in the end I just couldn't get over the issues I had with the core of the language runtime.
- diggan 6y agoExceptions and stack traces I agree with you can be a bit ridiculous, probably because I'm not used to Java at all. > Also, I take issue with a language that touts itself as purely functional Seems to be a common misconception that still hasn't died. Clojure doesn't tout itself as a "purely functional" language, and as far as I know, never has. It tout itself as a "practical general purpose" language where you can be pure and impure, depending on what you do. What Clojure does advocate for, is the approach that _most_ parts of _most_ programs should functional, but you should be able to go away from that paradigm when required/wanted. > It places a lot of trust on the libraries that make up your program not to go into reflection and do some really annoying mutations Just for the record, in reality and practical terms, I've never had this happen to me. Now I haven't done Clojure development for more than 2 years or something, but if it was a real problem, I'm guessing I would have hit this at least once before. But never have I had a Clojure library unexpectedly mutate things it wasn't supposed to. So yeah, if you're looking for a purely functional language, go with a language that actually tries to be purely functional, because that's not what Clojure aims for, it aims for practicality.
- holtalanm 6y ago> Exceptions and stack traces I agree with you can be a bit ridiculous, probably because I'm not used to Java at all. Even if you are used to java, the exceptions and stack traces in Clojure still don't make sense. This is coming from someone who was writing Java in their day job while learning Clojure at home. > Seems to be a common misconception that still hasn't died. Probably because it is not a misconception? Right on the Clojure main site, it states it is a functional language, and that Object Oriented programming is overrated. With the language being built on top of the JVM you _cannot_ avoid objects (the bytecode generated by Clojure is riddled with objects). Clojure is a language that claims to be functional while building its foundations upon one of the most well-known object-oriented systems out there. This is like building a house on top of a concrete foundation, laying some boards over the top to cover it up, and claiming the house is 100% wood. It just....isn't. It also makes the claim that Clojure data structures are immutable. That is 100% not true, as ANY object or data structure can be mutated on the JVM at runtime with reflection. If Clojure truly doesn't aim to be a functional programming language, then maybe they need to update their website. > Just for the record, in reality and practical terms, I've never had this happen to me. If you use any java libraries in your Clojure projects, there is a very high chance you will run into this. One of the 'strengths' that Clojure lays claim to is being able to leverage the Java ecosystem, while at the same time apparently also claiming that you shouldn't use libraries from Java (or if you do, write a wrapper for it).
- jtms 6y agoRuby used to be my primary language for many years and I used its REPL extensively in my day to day and found it immensely useful. Is Clojure's REPL different/better than the IRB and pry REPL workflow?
- diggan 6y agoYes, absolutely. Either it's wrong to call IRB/pry a REPL, or it's wrong to call what Clojure gives you a REPL, unsure of which one. But basically there is a massive difference. Basically the Clojure REPL is not another process you type into, then you copy paste code into your editor. No, you usually write code like you do in your editor, then you can select snippets of code that gets evaluated in the REPL, in the context of your application, with all the running state already there. I advice you to take a look at the link in my previous comment, which explains it better than I can, and also adds more information about why the Clojure REPL is so different, especially if you embrace it in your development workflow. In case you missed it, here is the link again: https://vvvvalvalval.github.io/posts/what-makes-a-good-repl.html https://vvvvalvalval.github.io/posts/what-makes-a-good-repl....
- jtms 6y agoDoh... I should actually read and not just gloss. Sorry about that! I'll check out that link, thanks for the reply :) (replying as a sibling as I suppose we have hit maximum depth)