4 ms·
I'm not sure why Yegge is talking about the Shangri-la of non-local exits, but... He is right that the culture of Clojure has some issues and often rejects idea
by KirinDave 16y ago
I'm not sure why Yegge is talking about the Shangri-la of non-local exits, but... He is right that the culture of Clojure has some issues and often rejects ideas even when they're obvious, and it's not clear why.
Examples I've run into:
1. The current clojure lambda shortcut-syntax is atrocious, and we can do better. Why don't we do better?
2. Clojure could really benefit from a scheme-esque Macro-by-example library. A few exist but they seem largely ignored by the community; despite well-known-benefits to such a system in the normal daily use of macros.
3. A strange hatred of macros. Yes, some people are reasonable and argue that functions should have primacy over macros because of composability (and they're right). But then there are people who will tell you macros are always bad, and if you show up in freenode #clojure to ask for help with them they will actively laugh at you.
I love Clojure and I feel like I know it pretty well, so I'm not trying to say Clojure is considered harmful, etc. But I do think that some of Yegge's criticisms—while poorly delivered and sometimes poorly expressed—have an element of truth to them.
* Full disclosure: I was involved in an effort to write a Clojure book for O'Reilly until I got involved with a new startup and had to terminate my involvement in the effort. I may not be the most unbiased judge of Clojure.
- gruseom 16y agoif you show up in freenode #clojure to ask for help with them they will actively laugh at you Oh dear. That is a bad sign. It has always seemed to me that building a healthier community from the ground up was the biggest thing a successful new Lisp would have to offer. The behavior you describe is all too reminiscent. No one should ever be "actively laughed at" for asking an honest question, and Clojure experts (if they know what's good for them) ought to take an aggressive stance against that kind of behavior. These communities are delicate things. They can become diseased. It makes me mad to see anyone get "actively laughed at", let alone by bullies who assuage the beast of their own insecurity by doing the intellectual equivalent of beating up children. Edit: oh, and: they're being laughed at for asking about macros? This is a Lisp, right?
- swannodette 16y agoThe best way to deal with trolls is to simply not feed them. My experience on Clojure IRC the past 3 years is that its orders of magnitude less condescending than the Python, Ruby, or Node.js IRC channels.
- gruseom 16y agoOh good. That's exactly what I was hoping someone who knows would say. Edit: I'm not talking about trolls, though, but about respected members of a community acting this way. If bullying is confined to trolls, along with all the other bad things trolls do, that's a healthy sign.
- KirinDave 16y agoI won't name names, but you'd know the names I could name. It is true that, so long as you stay away from a few key third rails, the #clojure channel is generally a great place. One need only to go to #scala on a bad day to see what a few bad actors can do to make a place feel oppressive. There's no value in such arguments tho. It's an undeniable truth that the Clojure community (and its libraries) are far less macro-friendly and macro-centric than other lisps. Even PLT Scheme seems more comfortable with defmacro usage.
- puredanger 16y agoThere's a joke here about Scala and actors, I'm just sure of it.
- swannodette 16y ago1. I'm curious as to what you think would be better? 2. Would be nice, but I think a high level of macro-understanding is not broadly distributed yet in the Clojure community, so scheme-esque macro libraries for most people seem like "yet another thing to learn". 3. I don't find this to be the case in general at all.
- KirinDave 16y ago1. Scala certainly has a better in-place lambda syntax. Way better. //; someNumbers is a vector of numbers someNumbers.reduceLeft( _ + _ ) (reduce #(+ %1 %2) someNumbers) //; A more complex example someNumbers.foldLeft(0)(_ + _ * 2) (reduce #(+ %1 (* 2 %2)) 0 someNumbers) I'm fluent in prefix notation, but I still have to watch the clojure code that uses #() very carefully. 2. I think that Macros By Example would be a better tool for teaching macro than the raw compiler extensions that defmacro provides. MBE is easier, not harder. Defmacro is the machinery, not the interface for most tasks. 3. I won't name names, but I've had high-profile people in #clojure do exactly this to me. And when I barked back, I was told to not be rude. It was a terrible experience caused by a prominent member of #clojure who otherwise seems like a smart individual. I've since received commiserations from people who have faced similar condemnations. (note: added simplified example)
- papaf 16y agoSorry to pick nits but the clojure example could be: (reduce + some-numbers)
- deleted 16y ago[deleted]
- masklinn 16y agoSorry to pick nits, but you magnificently managed to completely miss his point.
- edw 16y agoWhat is so unreadable about '#(+ %1 (* 2 %2))'? Can Scala use arguments in an order other than the order in which they're given? If not, then Scala's simplicity is at the cost of less flexibility. If you find that too hairy, just write '(fn [a b] (+ a (* 2 b)))'. The shortcut syntax is intended for simple cases.
- fogus 16y agoWithin any culture there are individuals who will act like dickweeds. Likewise, not every feature that you propose is likely to be accepted. Are these cultural problems?
- KirinDave 16y agoI'm not saying someone in #clojure was a meanie, therefore clojure is doomed.
- fogus 16y agoI'm not trying to give you a hard time, I really am curious about the answer. These kinds of discussions tend to be anecdotal (understandably so) or too nebulous and so I'm trying to dive deeper.
- KirinDave 16y agoExamples: I'll be honest: the direction 1.3 went was not a direction I saw as valuable. Similarly, I felt like the 1.2 work on protocols and datatypes was about 3/5 of what a person would need to use them in general programming. I've talked with some people I consider experts in Clojure and they suggested to me they have some similar feelings. The community dislike of macros, and a curious insistance on using the most difficult and bug-prone version (not to mention least debuggable) of a macro implementation is another example of a troubling bias in the direction of clojure. I am not a genius, nor do I claim to have superior information on which direction Clojure should go. All I have is my biases and intuitions, but I don't think I'm alone in their current values.
- swannodette 16y agoWhat exactly did you not like about 1.3? It's faster and a lot numeric stuff no longer needs to be written Java. As far as 1.2, the only thing I find lacking around protocols and datatypes is reader support and a default constructor fn. As far as community dislike of macros, I'm not convinced. I also don't see anything stopping anyone from submitting their CA and pitching a friendlier macro front-end. But as far I can tell most people in the Clojure community are not familiar with Scheme style macros. You'd have to come up with the code, write the tutorials, and market your approach. That it's a lot of work is the only reason I see that it hasn't been done yet - not because anyone is against the idea.
- arohner 16y ago> if you show up in freenode #clojure to ask for help with them they will actively laugh at you. #clojure has consistently been one of the most helpful resources for me, and the most helpful IRC channel I've ever been in. I've never seen anyone laughed at there.
- Rayne 16y agoThat is a silly thing to say. I've never seen a language that had such a friendly community. I don't think that in my two years of being active in the Clojure community, I have ever seen a single person get 'laughed at' for any reason at all. Sure, there are trolls every now and then. You can't control everybody. The ratio of trolls to helpful participants is excellent and always has been.
- cemerick 16y agoThere is a spike of scheme-esque macros for Clojure here: https://github.com/qbg/syntax-rules https://github.com/qbg/syntax-rules Not sure of the status/quality of that impl, but there you go.