3 ms·
Just saw this tweet from Rich Hickey [1]: > If you think you know how I ought to spend my time, come over and mow my lawn while I expound on the problems of de
by slantedview 10y ago
Just saw this tweet from Rich Hickey [1]:
> If you think you know how I ought to spend my time, come over and mow my lawn while I expound on the problems of dev entitlement culture.
All due respect, but I don't think Rich gets it.
Other people are spending _their own_ time as well, researching, writing and reporting issues, and in many cases, would be perfectly happy to submit fixes for those issues (and in some cases, they have). It doesn't take any more work for Rich or someone else to look at an issue and say, yes, this is a problem and thank you for fixing it, then it does to say screw you, WontFix. And that is where Clojure has a problem.
Rich's argument is really a strawman. Nobody is telling him what to fix, but neither can anyone force him to recognize the importance of fixing long outstanding bugs _in his own work_, even if, thanks to a great community, fixing those bugs wouldn't require him to lift a finger.
1: https://twitter.com/richhickey/status/741982205392617472 https://twitter.com/richhickey/status/741982205392617472
- nikofeyn 10y agoi saw that too. it seems to be a rather childish response. i have recently become very excited about clojure as someone new to it since there are some greatn resources for the language in the form of books (even one on frp), but this ordeal and the clojure people's response has turned me off of it. it seems all peopme are really crying out for is clear and accurate communication. i mentioned this in another comment that this attitude is a stark contrast to the f# and racket communities.