My Increasing Frustration with Clojure

Post by dang » Sat, Jun 11, 2016, 10:19 PM UTC

pdimitar wrote: post #109

calibraxis wrote: post #58

Earlier quoted context omitted.

Critiques from Clojure users should really try tradeoff analysis, as Hickey advocates. Which means I should analyze the costs of what I advocate, not just the benefits. For clojure.set/intersection (CLJ-1682?), Alex Miller clearly mentioned the speed consideration — one all users would have to bear. Not to mention spending time on this versus other things. Also, it was ironic to read elsewhere in the article, "Even m…

You're right and make a very good point. But that doesn't change the fact that there are bugs from 2009 which barely have comments or even a reasonable explanation. Me being a pretty average typer (~95 WPM) I could type 2-3 paragraphs detailing why I am against fixing anything, in no more than 6-8 minutes. So for 7 years such bugs to never even get a proper explanation is showing the maintainers as douchebags, not vi…

Post by MustardTiger » Sat, Jun 11, 2016, 10:21 PM UTC

hugdru wrote: post #55

gabrielc wrote: post #48

I think elixir is a better choice.

I was thinking of learning a modern language for the web back end. After analysing elixir, go and clojure I decided to go for clojure. Uhmmm, maybe go? I don't know :X. Stick with php? Meehhh

Post by village-idiot » Sat, Jun 11, 2016, 10:33 PM UTC

brandonbloom wrote: post #85

Clojure is a language for people who know what they are doing by people who know what they are doing. If you're giving sequences to the set functions, you either (A) don't know what you're doing or (B) have yet to discover that clojure.set is not what you want. Set union can't be done efficiently on arbitrarily sized sequences. At least one of the two arguments needs to offer fast set membership; ideally the larger o…

Post by village-idiot » Sat, Jun 11, 2016, 10:38 PM UTC

blain_the_train wrote: post #76

> And the namespace is completely riddled with bugs. union returns duplicates if some of the inputs are lists instead of sets depending on their length. to be clear I assume he is taking about this: ``` try-spec.core=> (clojure.set/union [1,2] [1,2]) [1 2 1 2] ``` Though im not sure what "depending on their length means". > for the above bugs there are two possible fixes: raise an IllegalArgumentException if anything…

Post by lgrapenthin » Sat, Jun 11, 2016, 10:59 PM UTC

dlandis wrote: post #156

lgrapenthin wrote: post #69

As a dev programming in Clojure professionally day to day this complaint (core team not fixing/prioritizing bugs) seems absurd to me. The only example given for a bug is not even a bug but undefined behavior triggered by undocumented API usage. If the author means clojure.spec by "greenfield development" (I don't see what else he could mean) he should really reconsider his complaint since clojure.spec is going to do…

> The only example given for a bug is not even a bug but undefined behavior triggered by undocumented API usage You only saw one example bug? He linked to 5 tickets in the section "show stopping bugs remain untouched".