4 ms·

I think the author is right in his assessment that it's a community problem: the Clojure core team does not want outsiders to participate in the future of the l

by _pmf_ 10y ago

I think the author is right in his assessment that it's a community problem: the Clojure core team does not want outsiders to participate in the future of the language, but does not clearly communicate this up front. I absolutely support the right for them to do this (I'm a happy user of the non-open C# language, after all), but they should clearly state that Clojure is defined by Cognitect, not the community. Even one of the most prolific Clojure users with a tremendous track record of extremely well engineered and practically useful libraries, Zach Tellman, has been bitten by Rich Hickey's / the core team's NIH syndrome[0]. That's no way to treat the people who love your language. [0] http://dev.clojure.org/jira/browse/CLJ-1517 http://dev.clojure.org/jira/browse/CLJ-1517

twoodfin 10y ago
What's the problem with [0]? I am not a Clojure expert, nor have I looked in detail at the patch, but Rich's concerns about megamorphic call sites in library code sound plausible.
btown 10y ago
While I don't know enough about Clojure politics to weigh in on general NIH trends, this specific patch actually has a strong rationale for further debate before acceptance. http://dev.clojure.org/jira/browse/CLJ-1517?focusedCommentId=40370&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-40370 http://dev.clojure.org/jira/browse/CLJ-1517?focusedCommentId...
snaky 10y ago
> but does not clearly communicate this up front Author of Clojure fork (cursive is mine) > Clojure is Rich's personal project, which he is so kind as to share with the rest of us and in in its refinement Rich chooses to accept some amount of input from us as users. I'm somewhat ashamed to admit that it took me two years to realize this https://www.arrdem.com/2016/02/22/clojarr_-_a_friendly_clojure_fork/ https://www.arrdem.com/2016/02/22/clojarr_-_a_friendly_cloju...

by _pmf_ 10y ago

twoodfin 10y ago

What's the problem with [0]? I am not a Clojure expert, nor have I looked in detail at the patch, but Rich's concerns about megamorphic call sites in library code sound plausible.

btown 10y ago

While I don't know enough about Clojure politics to weigh in on general NIH trends, this specific patch actually has a strong rationale for further debate before acceptance. http://dev.clojure.org/jira/browse/CLJ-1517?focusedCommentId=40370&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-40370 http://dev.clojure.org/jira/browse/CLJ-1517?focusedCommentId...

snaky 10y ago

> but does not clearly communicate this up front Author of Clojure fork (cursive is mine) > Clojure is Rich's personal project, which he is so kind as to share with the rest of us and in in its refinement Rich chooses to accept some amount of input from us as users. I'm somewhat ashamed to admit that it took me two years to realize this https://www.arrdem.com/2016/02/22/clojarr_-_a_friendly_clojure_fork/ https://www.arrdem.com/2016/02/22/clojarr_-_a_friendly_cloju...