Need help?
<- Back

Comments (43)

  • meken
    This year has been fun for learning programming languages that change the way I think. The highlights have been:- Clojure for functional programming (you mean you can update a bitmap in a purely functional way??)- Array langauges (APL, BQN, J) for avoiding loops with matrix operations- Prolog for avoiding loops with backtracking
  • TN1ck
    There was a time in university where I started my days with doing some 4clojure puzzles. I became so obsessed, I managed to solve almost all of them. It's wild what an impact these few weeks had on my programming abilities. It's a beautifully designed language that makes you think in data structures and their transformations.As a side note: I code Clojure in Lightroom. It was so cool to see your code instantly evaluate and trace through your functions.
  • podgorniy
    The interesting thing about Clojure, for me, is that for all its beauty and power, it’s so simple that there isn’t much variety in the articles you can write or the “gotchas” you can cover for a wide audience. Niche stuff that assumes you already know Clojure doesn’t catch on with a wider audience. Its strong points—“everything is data,” “REPL development,” “immutability and strong primitives,” and “paradigm shift”—get repeated so often that they become noise people just filter out.There isn’t much room for yet another framework or another way to work with data (I’m looking at you, Node.js), so there isn’t much to talk about or write articles about.In other words, the efficiency and simplicity of the language act as a barrier to its spread in a world where only repeated mentions get through. IDK, maybe this is for the better after all.
  • sourdecor
    I recently found out you can use Malli type providers[0] with Typed Clojure[1] to get instant feedback when developing!So you can do this when programming: (m/=> foo [:=> [:cat :int] :int]) (defn foo [t] (inc t)) (foo 1) [0]: https://github.com/typedclojure/typedclojure/tree/main/examp...[1]: https://github.com/typedclojure/typedclojure
  • tikotus
    In the era of LLMs, I often stop to think of Clojure. I believe it had a significant role in popularizing the concept of immutable data structures. Immutability simplifies the required context for understanding and solving problems. This benefits both humans and LLMs.Would an LLM, or a person solely coding using them, have had the insight to work out that immutability is the way to go, and we should revolutionize software develoment? If LLMs had happened 15 years ago, would all code still be "place oriented programming", with higher token counts and less reliability than we have today thanks to better practices we've learned in the recent past?If so, what are we missing out on in the future, now that stopping and thinking about code is frowned upon?
  • ajasmin
    I love the thoughtful approach to programming that Clojure exemplify.MVP churn and AI fatigue is getting to me. Need some good Hammock Time!
  • darksaints
    By a weird stroke of luck, clojure was one of the first languages I learned. And yeah, I guess it left a lasting impact on me in the form of an appreciation for immutability and dataflow programming.Unfortunately it also left me with an extremely deep distaste for dynamic types, and in particular, the blind usage of lists and maps for everything. The ML family of languages finally gave me a paradigm worth keeping around.
  • Jtsummers
    https://news.ycombinator.com/item?id=14928429 - One discussion from back then, 216 comments
  • opiniateddev
    fun fact: Conductor OSS has support for clojurehttps://github.com/conductor-oss/clojure-sdk
  • shevy-java
    So, people say this about programming languages all the time.My problem is:a) this assumes that people can not have ideas without a programming languages. That's obviously incorrect. I can have ideas without knowing a programming language.b) languages also constrain the thinking. For instance, in ruby you have a class and a module, as distinction. Is that a useful distinction? I think it is overlapping, with modules giving more flexibility. In practice, this distinction does not lead to many problems, but if you have: class Foo; module Bar; end; end and then you were to write "class Foo::Bar" in another file because you want to modify the code quickly, then ruby says you'd have to use "module Foo::Bar" instead, because the ruby parser already knew that this is a module, not a class. It is not a big problem, but whenever I run into this issue, I wonder why I need to care whether it is a class, or a module. Because, when I do so, such as adding a new method to that, perhaps from another namespace/project, then I wonder why ruby does not prioritize me wanting to change the code, but instead complains about that it is a module or a class. (I understand the ruby parser has to work that way, in order to differentiate between errors made or mixing up code, but my point of contention here is the "class versus module" distinction. The above is one example of many more that can be found in programming languages.Of course you can reason that better programming languages typically lead to better implementations too. I'd reason in favour of such a statement. I don't really see the point of learning a language that is inferior to languages I already know, when I know I am not going to use that language. The "learn a new language every year" is not a bad idea, but why would I want to learn languages that are bad? That makes no sense. There is competition between languages, as well as against time.
  • theanonymousone
    To me, Clojure was "Lisp for JVM". Is that an incorrect picture?I mean, recently I saw Clojure for . Net and Clojure without JVM (forgot the name). If you don't need/want JVM, then why would you use Clojure over e.g. Common Lisp?
  • deterministic
    If you enjoy your brain exploding then I also highly recommend learning LEAN and how to prove software correct.
  • ConanRus
    [dead]
  • stephbook
    I think clojurists overestimate how advanced their language is. Or maybe it's just my outsider's perspective? Famously, Clojurists/Lispers think that theirs is the most advanced language and everyone who fails to see that just doesn't understand expressive power.In any case: Typescript has dynamic types and static types, it has true union types, it has hot reload (what you might call REPL), it has the widest package ecosystem and so much more. It works out of the box with the most popular IDE and you don't need to learn emacs.I rarely hit the power ceiling of Typescript, so I never put in the work to learn Clojure.
  • zergrush
    Outdated article post-LLMs, if you are still taking to heart what this article says you are working against the trend.You don't need any inner working of clojure or any lower language for that matter. It's all available within your reach. Don't let the people who have built an identity over the tools that they have chosen, they can't give you any meaningful advice anymore with what we have as tools.I'm saying this as someone who has worked with clojure for over a decade. There is no point in gate keeping things anymore. It also means that the point of clojure which is supposed to have a lot of DX built into it , is gone with LLMs.Software is largely solved now and the only thing that matters now is distribution so start thinking about your product and how to market it.
  • chao86825
    [flagged]
  • bibimsz
    [flagged]